CVE-2013-0401

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

A fix is available — apply it.

The Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, and 5.0 Update 41 and earlier; and OpenJDK 6 and 7; allows remote attackers to execute arbitrary code via vectors related to AWT, as demonstrated by Ben Murphy during a Pwn2Own competition at CanSecWest 2013. NOTE: the previous information is from the April 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to invocation of the system class loader by the sun.awt.datatransfer.ClassLoaderObjectInputStream class, which allows remote attackers to bypass Java sandbox restrictions.

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

Published

March 8, 2013

Last Modified

April 29, 2026

References (62)

Vendor Advisories for CVE-2013-0401(1)

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.5-0ubuntu0.12.04.1) @ precise2026-05-29ubuntu
ubuntuopenjdk-7-jre (7u21-2.3.9-0ubuntu0.12.10.1) @ quantal2026-05-29ubuntu
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.2-1jpp.1.el6_42013-05-22redhat
redhatjava-1.6.0-ibm-1:1.6.0.13.2-1jpp.1.el6_42013-05-14redhat
redhatjava-1.7.0-ibm-1:1.7.0.4.2-1jpp.1.el6_42013-05-14redhat
redhatjava-1.6.0-openjdk-1:1.6.0.0-1.61.1.11.11.el6_42013-04-24redhat
redhatjava-1.7.0-oracle-1:1.7.0.21-1jpp.1.el62013-04-18redhat
redhatjava-1.6.0-sun-1:1.6.0.45-1jpp.1.el62013-04-18redhat
redhatjava-1.7.0-openjdk-1:1.7.0.19-2.3.9.1.el5_92013-04-17redhat
redhatjava-1.7.0-openjdk-1:1.7.0.19-2.3.9.1.el6_42013-04-17redhat

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(11)

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

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2013-0401?
CVE-2013-0401 is a none vulnerability published on March 8, 2013. The Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, and 5.0 Update 41 and earlier; and OpenJDK 6 and 7; allows remote attackers to execute arbitrary code via vectors related to AWT, as demonstrated by Ben Murphy during a Pwn2Own…
When was CVE-2013-0401 disclosed?
CVE-2013-0401 was first published in the National Vulnerability Database on March 8, 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-0401 actively exploited?
CVE-2013-0401 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-0401?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-0401, 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-0401

Explore →

Is Your Infrastructure Affected by CVE-2013-0401?

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

Start Free Scan →Browse All CVEs