CVE-2018-3004 json
Vulnerability in the Java VM component of Oracle Database Server.
published 2018-07-18 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-14859
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Vulnerability in the Java VM component of Oracle Database Server. Supported versions that are affected are 11.2.0.4, 12.1.0.2,12.2.0.1 and 18.2. Difficult to exploit vulnerability allows low privileged attacker having Create Session, Create Procedure privilege with network access via multiple protocols to compromise Java VM. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Java VM accessible data. CVSS 3.0 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N).
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
2.64% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- obtruse.syfrtext.com http://obtruse.syfrtext.com/2018/07/oracle-privilege-escalation-via.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:P/I:N/A:N |
Affected products
- Oracle Corporation Oracle Database
Classification
- Technology feeds
References
-
oracle.com
/technetwork/security-advisory/cpujul2018-4258247.html
patch, vendor-advisory
-
obtruse.syfrtext.com
/2018/07/oracle-privilege-escalation-via.html
exploit, third-party-advisory
-
securitytracker.com
/id/1041299
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/104805
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-3004
- NVD CVE-2018-3004
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.