CVE-2013-2473

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 7.5% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 7.5%CVSS v2: 10.0Exploit: None knownExposed services: Not assessed

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 ByteBandedRaster size checks" in 2D.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
52
EG Risk 52/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation8% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
7.5%
EPSS %ILE
94th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 18, 2013

Last Modified

April 29, 2026

References (62)

Vendor Advisories for CVE-2013-2473(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenjdk-6-jre-lib (6b27-1.12.6-1ubuntu0.12.04.2) @ precise2026-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.7.0-ibm-1:1.7.0.5.0-1jpp.2.el6_42013-07-15redhat
redhatjava-1.6.0-ibm-1:1.6.0.14.0-1jpp.1.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-openjdk-1:1.7.0.25-2.3.10.4.el5_92013-06-20redhat
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.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.

Affected Packages

(3 across 2 ecosystems)
Debian:7(2)
PackageVulnerable rangeFix by version rangeDependents
openjdk-66b27-1.12.5-1, 6b27-1.12.5-2, 6b27-1.12.6-1~deb6u1
  • every version up to 6b27-1.12.6-1~deb7u1: fixed in 6b27-1.12.6-1~deb7u1
—
openjdk-77u13-2.3.6-1 ... 7u9-2.3.5~pre1-1 (16 versions)
  • every version up to 7u25-2.3.10-1~deb7u1: fixed in 7u25-2.3.10-1~deb7u1
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-66b18-1.8.10-0+squeeze1 ... 6b27-1.12.5-2 (73 versions)
  • every version up to 6b27-1.12.6-1~deb6u1: fixed in 6b27-1.12.6-1~deb6u1
—

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 3× in last 7d / 12× 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.

Showing the most recent 100 of 127 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2013-2473?
CVE-2013-2473 is a high 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-2473 disclosed?
CVE-2013-2473 was first published 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-2473 actively exploited?
CVE-2013-2473 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.5% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
How do I remediate CVE-2013-2473?
A fix for CVE-2013-2473 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2013-2473 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-2473

Explore →

Is Your Infrastructure Affected by CVE-2013-2473?

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

Book a Demo →Browse All CVEs