CVE-2013-2471

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 15%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 21 and earlier, 6 Update 45 and earlier, and 5.0 Update 45 and earlier, and OpenJDK 7, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D. NOTE: the previous information is from the June 2013 CPU. Oracle has not commented on claims from another vendor that this issue allows remote attackers to bypass the Java sandbox via vectors related to "Incorrect IntegerComponentRaster size checks."

CVSS v3
—
EG Score
0.0(none)
EPSS
96.3%
KEV
Not listed

Published

June 18, 2013

Last Modified

April 29, 2026

References (62)

Vendor Advisories for CVE-2013-2471(2)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenjdk-6-jre-lib (6b27-1.12.6-1ubuntu0.10.04.2) @ lucid2026-05-28ubuntu
ubuntuopenjdk-7-doc (7u25-2.3.10-1ubuntu0.13.04.2) @ raring2026-05-28ubuntu
redhatjava-1.6.0-sun-1:1.6.0.75-1jpp.1.el6_52014-04-17redhat
redhatjava-1.6.0-ibm-1:1.6.0.14.0-1jpp.1.el5_92013-10-23redhat
redhatjava-1.5.0-ibm-1:1.5.0.16.3-1jpp.1.el6_42013-07-16redhat
redhatjava-1.6.0-ibm-1:1.6.0.14.0-1jpp.1.el6_42013-07-15redhat
redhatjava-1.7.0-ibm-1:1.7.0.5.0-1jpp.2.el6_42013-07-15redhat
redhatjava-1.6.0-openjdk-1:1.6.0.0-1.62.1.11.11.90.el6_42013-07-03redhat
redhatjava-1.7.0-oracle-1:1.7.0.25-1jpp.1.el6_42013-06-20redhat
redhatjava-1.7.0-openjdk-1:1.7.0.25-2.3.10.4.el5_92013-06-20redhat
redhatjava-1.7.0-openjdk-1:1.7.0.25-2.3.10.3.el6_42013-06-19redhat

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.

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 29× 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-05 02:26 UTCEPSS rescore
  2. 2026-07-04 06:27 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-06-30 23:19 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-29 14:02 UTCEPSS rescore
  7. 2026-06-28 14:03 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-27 03:05 UTCEPSS rescore
  11. 2026-06-25 13:46 UTCEPSS rescore
  12. 2026-06-24 14:02 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-23 21:30 UTCEPSS rescore
  15. 2026-06-21 14:53 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-21 01:56 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-18 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-17 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-16 17:49 UTCEPSS rescore
  24. 2026-06-15 17:44 UTCEPSS rescore
  25. 2026-06-13 22:57 UTCEPSS rescore
Show 42 more
  1. 2026-06-12 23:08 UTCEPSS rescore
  2. 2026-06-11 13:56 UTCEPSS rescore
  3. 2026-06-10 13:18 UTCEPSS rescore
  4. 2026-06-08 14:14 UTCEPSS rescore
  5. 2026-06-05 22:44 UTCEPSS rescore
  6. 2026-06-05 22:44 UTCEPSS rescore
  7. 2026-06-05 06:08 UTCEPSS rescore
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-02 20:10 UTCEPSS rescore
  10. 2026-06-02 20:10 UTCEPSS rescore
  11. 2026-06-01 13:49 UTCEPSS rescore
  12. 2026-06-01 13:49 UTCEPSS rescore
  13. 2026-05-31 22:28 UTCEPSS rescore
  14. 2026-05-31 22:28 UTCEPSS rescore
  15. 2026-05-31 00:14 UTCEPSS rescore
  16. 2026-05-31 00:14 UTCEPSS rescore
  17. 2026-05-29 13:41 UTCEPSS rescore
  18. 2026-05-29 13:41 UTCEPSS rescore
  19. 2026-05-28 23:34 UTCEG score recompute
  20. 2026-05-28 23:34 UTCVendor advisory
  21. 2026-05-28 23:34 UTCGHSA enrichment
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-28 13:42 UTCEPSS rescore
  24. 2026-05-28 13:42 UTCEPSS rescore
  25. 2026-05-27 13:38 UTCEPSS rescore
  26. 2026-05-27 13:38 UTCEPSS rescore
  27. 2026-05-26 13:41 UTCEPSS rescore
  28. 2026-05-26 13:41 UTCEPSS rescore
  29. 2026-05-26 07:16 UTCEPSS rescore
  30. 2026-05-26 07:16 UTCEPSS rescore
  31. 2026-05-24 16:43 UTCEPSS rescore
  32. 2026-05-22 21:15 UTCEPSS rescore
  33. 2026-05-22 21:15 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-21 22:39 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 11:21 UTCEPSS rescore
  39. 2026-05-20 11:21 UTCEPSS rescore
  40. 2026-05-20 11:21 UTCEPSS rescore
  41. 2026-05-18 21:29 UTCEPSS rescore
  42. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2013-2471?
CVE-2013-2471 is a none vulnerability published on June 18, 2013. Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 21 and earlier, 6 Update 45 and earlier, and 5.0 Update 45 and earlier, and OpenJDK 7, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to…
When was CVE-2013-2471 disclosed?
CVE-2013-2471 was first published in the National Vulnerability Database on June 18, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-2471 actively exploited?
CVE-2013-2471 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-2471?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-2471, 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-2013-2471

Explore →

Is Your Infrastructure Affected by CVE-2013-2471?

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

Start Free Scan →Browse All CVEs