CVE-2017-3248

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2017-12369 (ENISA EUVD) · GHSA-j377-ff8h-jf66 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 97%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 97%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Core Components). Supported versions that are affected are 10.3.6.0, 12.1.3.0, 12.2.1.0 and 12.2.1.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS v3.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts).

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
98
EG Risk 98/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation97% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
97%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
97% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 27, 2017

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Oct 17, 2026
Fix referenced — no release confirmed yet.
Web page

CVE-2017-3248 - PSIRT.COM

http://www.securityfocus.com/bid/95465
Web page

[R1] Oracle WebLogic RMI Registry UnicastRef Object Java Deserialization Remote Code Execution - Research Advisory | Tenable®

https://www.tenable.com/security/research/tra-2017-07
Web page

Oracle WebLogic 12.1.2.0 - RMI Registry UnicastRef Object Java Deserialization Remote Code Execution - Multiple webapps Exploit

https://www.exploit-db.com/exploits/44998/

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 151 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 51 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 09:50 UTCEchelonGraph re-scored
  2. 2026-11-22 09:50 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-21 10:03 UTCEchelonGraph re-scored
  4. 2026-11-21 10:03 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-20 10:13 UTCEchelonGraph re-scored
  6. 2026-11-20 10:13 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-19 10:24 UTCEchelonGraph re-scored
  8. 2026-11-19 10:24 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-18 16:28 UTCEPSS rescoreEPSS 97% · 99th percentile
  10. 2026-11-18 10:28 UTCEchelonGraph re-scored
  11. 2026-11-18 10:28 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-17 10:41 UTCEchelonGraph re-scored
  13. 2026-11-17 10:41 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-16 16:35 UTCEPSS rescoreEPSS 97% · 99th percentile
  15. 2026-11-16 10:57 UTCEchelonGraph re-scored
  16. 2026-11-16 10:57 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-15 11:02 UTCEchelonGraph re-scored
  18. 2026-11-15 11:02 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-11-14 11:17 UTCEchelonGraph re-scored
  20. 2026-11-14 11:17 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-13 11:31 UTCEchelonGraph re-scored
  22. 2026-11-13 11:31 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-12 11:46 UTCEchelonGraph re-scored
  24. 2026-11-12 11:45 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-11-11 16:29 UTCEPSS rescoreEPSS 97% · 99th percentile
Show 75 more
  1. 2026-11-11 12:01 UTCEchelonGraph re-scored
  2. 2026-11-11 12:01 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-10 12:16 UTCEchelonGraph re-scored
  4. 2026-11-10 12:16 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-09 12:31 UTCEchelonGraph re-scored
  6. 2026-11-09 12:31 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-08 12:46 UTCEchelonGraph re-scored
  8. 2026-11-08 12:46 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-07 13:00 UTCEchelonGraph re-scored
  10. 2026-11-07 13:00 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-06 16:28 UTCEPSS rescoreEPSS 97% · 99th percentile
  12. 2026-11-06 13:15 UTCEchelonGraph re-scored
  13. 2026-11-06 13:15 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-05 13:31 UTCEchelonGraph re-scored
  15. 2026-11-05 13:31 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-04 16:28 UTCEPSS rescoreEPSS 97% · 99th percentile
  17. 2026-11-04 13:46 UTCEchelonGraph re-scored
  18. 2026-11-04 13:46 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-11-03 16:34 UTCEPSS rescoreEPSS 97% · 99th percentile
  20. 2026-11-03 14:01 UTCEchelonGraph re-scored
  21. 2026-11-03 14:01 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-11-02 14:04 UTCEchelonGraph re-scored
  23. 2026-11-02 14:04 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-01 14:18 UTCEchelonGraph re-scored
  25. 2026-11-01 14:18 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-31 14:33 UTCEchelonGraph re-scored
  27. 2026-10-31 14:33 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-30 14:49 UTCEchelonGraph re-scored
  29. 2026-10-30 14:49 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-29 15:03 UTCEchelonGraph re-scored
  31. 2026-10-29 15:03 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-28 15:18 UTCEchelonGraph re-scored
  33. 2026-10-28 15:18 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-27 15:34 UTCEchelonGraph re-scored
  35. 2026-10-27 15:34 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-26 15:38 UTCEchelonGraph re-scored
  37. 2026-10-26 15:38 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-25 16:27 UTCEPSS rescoreEPSS 97% · 99th percentile
  39. 2026-10-25 15:48 UTCEchelonGraph re-scored
  40. 2026-10-25 15:48 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-24 16:04 UTCEchelonGraph re-scored
  42. 2026-10-24 16:03 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-23 16:16 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-22 16:30 UTCEchelonGraph re-scored
  45. 2026-10-22 16:30 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-22 16:27 UTCEPSS rescoreEPSS 97% · 99th percentile
  47. 2026-10-21 16:22 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-20 16:37 UTCEchelonGraph re-scored
  49. 2026-10-20 16:36 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-19 16:47 UTCEchelonGraph re-scored
  51. 2026-10-19 16:47 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-18 16:51 UTCEchelonGraph re-scored
  53. 2026-10-18 16:51 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-18 12:13 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-18 10:32 UTCEchelonGraph re-scored
  56. 2026-10-17 11:42 UTCEchelonGraph re-scored
  57. 2026-10-17 11:42 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-16 16:29 UTCEPSS rescoreEPSS 97% · 99th percentile
  59. 2026-10-16 11:57 UTCEchelonGraph re-scored
  60. 2026-10-16 11:56 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-15 12:10 UTCEchelonGraph re-scored
  62. 2026-10-15 12:09 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-14 07:38 UTCEchelonGraph re-scored
  64. 2026-10-14 07:37 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-13 16:27 UTCEPSS rescoreEPSS 97% · 99th percentile
  66. 2026-10-13 02:51 UTCGHSA enrichmentGHSA-j377-ff8h-jf66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-12 20:29 UTCEchelonGraph re-scored
  68. 2026-10-12 00:52 UTCEchelonGraph re-scored
  69. 2026-09-30 14:59 UTCEPSS rescoreEPSS 97% · 99th percentile
  70. 2026-09-30 09:33 UTCEchelonGraph re-scored
  71. 2026-09-24 13:59 UTCEPSS rescoreEPSS 97% · 99th percentile
  72. 2026-09-06 13:43 UTCEPSS rescoreEPSS 97% · 99th percentile
  73. 2026-09-05 15:23 UTCEPSS rescoreEPSS 91% · 99th percentile
  74. 2026-08-30 19:13 UTCEPSS rescoreEPSS 97% · 99th percentile
  75. 2026-08-25 13:44 UTCEPSS rescoreEPSS 97% · 99th percentile

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry), as are 2 GitHub checker repositories. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Metasploitexploit/multi/misc/weblogic_deserialize_unicastref✓ verified
    Published Apr 1, 2019

    Oracle Weblogic Server Deserialization RCE - RMI UnicastRef

    Open source ↗
  • GitHub checker0xn0ne/weblogicScanner
    Published Jan 15, 2020

    weblogic 漏洞扫描工具。目前包含对以下漏洞的检测能力:CVE-2014-4210、CVE-2016-0638、CVE-2016-3510、CVE-2017-3248、CVE-2017-3506、CVE-2017-10271、CVE-2018-2628、CVE-2018-2893、CVE-2018-2894、CVE-2018-3191、CVE-2018-3245、CVE-2018-3252、CVE-2019-2618、CVE-2019-2725、CVE-2019-2729、CVE-2019-2890、CVE-2020-2551、CVE-2020-14750、CVE-2020-14882、CVE-2020-14883

    Open source ↗
  • GitHub checkerdaybreak-kits/weblogicScanner
    Published Jan 15, 2020

    weblogic 漏洞扫描工具。目前包含对以下漏洞的检测能力:CVE-2014-4210、CVE-2016-0638、CVE-2016-3510、CVE-2017-3248、CVE-2017-3506、CVE-2017-10271、CVE-2018-2628、CVE-2018-2893、CVE-2018-2894、CVE-2018-3191、CVE-2018-3245、CVE-2018-3252、CVE-2019-2618、CVE-2019-2725、CVE-2019-2729、CVE-2019-2890、CVE-2020-2551、CVE-2020-14750、CVE-2020-14882、CVE-2020-14883

    Open source ↗
  • Exploit-DBEDB-44998
    Published Jul 7, 2018

    Oracle WebLogic 12.1.2.0 - RMI Registry UnicastRef Object Java Deserialization Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2017-3248?
CVE-2017-3248 is a critical-severity vulnerability; its CVE record was published on January 27, 2017. Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Core Components). Supported versions that are affected are 10.3.6.0, 12.1.3.0, 12.2.1.0 and 12.2.1.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3 to…
When was CVE-2017-3248 made public?
CVE-2017-3248 was made public on January 17, 2017: that is the date its CVE record's CNA, Oracle, gives for when the vulnerability was made public. The CVE record itself was published on January 27, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-3248 actively exploited?
CVE-2017-3248 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 97% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-3248?
CVE-2017-3248 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-3248?
A fix for CVE-2017-3248 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-3248

Explore →

Is Your Infrastructure Affected by CVE-2017-3248?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.