CVE-2018-3211

MEDIUMNVD 6.66.6
EchelonGraph scoreMEDIUM confidence

Score 6.6 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.6Exploit: NoneExposed: 0

A fix is available — apply it.

Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: Serviceability). Supported versions that are affected are Java SE: 8u182 and 11; Java SE Embedded: 8u181. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Java SE, Java SE Embedded executes to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java SE, Java SE Embedded accessible data as well as unauthorized access to critical data or complete access to all Java SE, Java SE Embedded accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets (in Java SE 8), that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g. code installed by an administrator). This vulnerability can only be exploited when Java Usage Tracker functionality is being used. CVSS 3.0 Base Score 6.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).

CVSS v3
6.6
EG Score
6.6(medium)
EPSS
34.1%
KEV
Not listed

Published

October 17, 2018

Last Modified

November 21, 2024

Vendor Advisories for CVE-2018-3211(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjava-1.8.0-oracle-1:1.8.0.191-1jpp.1.el62018-10-24redhat
redhatjava-1.8.0-oracle-1:1.8.0.191-1jpp.1.el72018-10-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:16 UTCEG score recompute
  2. 2026-07-22 14:05 UTCEPSS rescore
  3. 2026-07-21 15:22 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 02:26 UTCEPSS rescore
  7. 2026-07-19 02:26 UTCEPSS rescore
  8. 2026-07-16 16:59 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-15 16:55 UTCEPSS rescore
  11. 2026-07-15 16:55 UTCEPSS rescore
  12. 2026-07-15 01:56 UTCEPSS rescore
  13. 2026-07-15 01:56 UTCEPSS rescore
  14. 2026-07-13 22:27 UTCEPSS rescore
  15. 2026-07-13 22:26 UTCEPSS rescore
  16. 2026-07-13 06:10 UTCEPSS rescore
  17. 2026-07-12 05:43 UTCEPSS rescore
  18. 2026-07-11 08:24 UTCEPSS rescore
  19. 2026-07-09 19:06 UTCEPSS rescore
  20. 2026-07-08 15:11 UTCEPSS rescore
  21. 2026-07-07 13:42 UTCEPSS rescore
  22. 2026-07-07 13:42 UTCEPSS rescore
  23. 2026-07-06 16:24 UTCEPSS rescore
  24. 2026-07-06 16:24 UTCEPSS rescore
  25. 2026-07-06 02:20 UTCEPSS rescore
Show 73 more
  1. 2026-07-05 02:27 UTCEPSS rescore
  2. 2026-07-04 06:28 UTCEPSS rescore
  3. 2026-07-04 06:28 UTCEPSS rescore
  4. 2026-07-02 16:54 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-06-30 23:20 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-29 14:03 UTCEPSS rescore
  10. 2026-06-28 14:04 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-27 03:06 UTCEPSS rescore
  14. 2026-06-27 03:06 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-24 14:02 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-23 21:30 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 14:23 UTCEPSS rescore
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
  26. 2026-06-21 01:57 UTCEPSS rescore
  27. 2026-06-19 19:23 UTCEPSS rescore
  28. 2026-06-19 19:23 UTCEPSS rescore
  29. 2026-06-18 17:50 UTCEPSS rescore
  30. 2026-06-18 17:50 UTCEPSS rescore
  31. 2026-06-17 17:50 UTCEPSS rescore
  32. 2026-06-17 17:50 UTCEPSS rescore
  33. 2026-06-16 17:50 UTCEPSS rescore
  34. 2026-06-16 17:50 UTCEPSS rescore
  35. 2026-06-15 17:45 UTCEPSS rescore
  36. 2026-06-14 23:15 UTCEPSS rescore
  37. 2026-06-14 23:14 UTCEPSS rescore
  38. 2026-06-13 22:58 UTCEPSS rescore
  39. 2026-06-12 23:09 UTCEPSS rescore
  40. 2026-06-12 23:09 UTCEPSS rescore
  41. 2026-06-11 13:57 UTCEPSS rescore
  42. 2026-06-10 22:16 UTCEPSS rescore
  43. 2026-06-10 13:19 UTCEPSS rescore
  44. 2026-06-08 14:14 UTCEPSS rescore
  45. 2026-06-08 14:14 UTCEPSS rescore
  46. 2026-06-07 15:22 UTCEPSS rescore
  47. 2026-06-07 15:22 UTCEPSS rescore
  48. 2026-06-06 13:45 UTCEPSS rescore
  49. 2026-06-06 13:45 UTCEPSS rescore
  50. 2026-06-05 22:45 UTCEPSS rescore
  51. 2026-06-05 22:45 UTCEPSS rescore
  52. 2026-06-05 06:08 UTCEPSS rescore
  53. 2026-06-05 06:08 UTCEPSS rescore
  54. 2026-06-04 13:10 UTCEPSS rescore
  55. 2026-06-02 20:11 UTCEPSS rescore
  56. 2026-06-02 20:11 UTCEPSS rescore
  57. 2026-06-01 13:50 UTCEPSS rescore
  58. 2026-06-01 13:50 UTCEPSS rescore
  59. 2026-05-31 22:29 UTCEPSS rescore
  60. 2026-05-31 00:14 UTCEPSS rescore
  61. 2026-05-31 00:14 UTCEPSS rescore
  62. 2026-05-29 13:41 UTCEPSS rescore
  63. 2026-05-28 13:42 UTCEPSS rescore
  64. 2026-05-28 13:42 UTCEPSS rescore
  65. 2026-05-28 02:00 UTCEG score recompute
  66. 2026-05-28 02:00 UTCVendor advisory
  67. 2026-05-28 02:00 UTCGHSA enrichment
  68. 2026-05-27 13:38 UTCEPSS rescore
  69. 2026-05-27 13:38 UTCEPSS rescore
  70. 2026-05-26 13:42 UTCEPSS rescore
  71. 2026-05-26 13:42 UTCEPSS rescore
  72. 2026-05-26 07:17 UTCEPSS rescore
  73. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2018-3211?
CVE-2018-3211 is a medium vulnerability published on October 17, 2018. Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: Serviceability). Supported versions that are affected are Java SE: 8u182 and 11; Java SE Embedded: 8u181. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where…
When was CVE-2018-3211 disclosed?
CVE-2018-3211 was first published in the National Vulnerability Database on October 17, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-3211 actively exploited?
CVE-2018-3211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-3211?
CVE-2018-3211 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2018-3211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-3211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-3211

Explore →

Is Your Infrastructure Affected by CVE-2018-3211?

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