CVE-2013-0169

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

A fix is available — apply it.

The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, aka the "Lucky Thirteen" issue.

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

Published

February 8, 2013

Last Modified

April 29, 2026

References (110)

Vendor Advisories for CVE-2013-0169(2)

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

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenjdk-7-jre (7u15-2.3.7-0ubuntu1~12.10) @ quantal2026-05-29ubuntu
ubuntulibssl1.0.0 (1.0.1c-3ubuntu2.3) @ quantal2026-05-29ubuntu
ubuntulibssl1.0.0 (1.0.1c-3ubuntu2.1) @ quantal2026-05-29ubuntu
redhatopenshift4/ose-kube-rbac-proxy:v4.6.0-202010061132.p02020-10-27redhat
redhatspice-client-msi-0:3.3-122014-04-17redhat
redhatjava-1.6.0-ibm-1:1.6.0.14.0-1jpp.1.el5_92013-10-23redhat
redhatopenssl2013-07-03redhat
redhatjava-1.5.0-ibm-1:1.5.0.16.2-1jpp.1.el6_42013-05-22redhat
redhatjava-1.7.0-ibm-1:1.7.0.4.2-1jpp.1.el6_42013-05-14redhat
redhatjava-1.6.0-ibm-1:1.6.0.13.2-1jpp.1.el6_42013-05-14redhat
redhatpatch2013-05-01redhat
redhatpatch2013-05-01redhat
redhatrhev-hypervisor6-0:6.4-20130306.2.el6_42013-03-13redhat
redhatopenssl-0:1.0.0-27.el6_4.22013-03-04redhat
redhatjava-1.6.0-openjdk-1:1.6.0.0-1.35.1.11.8.el5_92013-02-20redhat
redhatjava-1.7.0-oracle-1:1.7.0.15-1jpp.1.el6_32013-02-20redhat
redhatjava-1.6.0-openjdk-1:1.6.0.0-1.56.1.11.8.el6_32013-02-20redhat
redhatjava-1.6.0-sun-1:1.6.0.41-1jpp.1.el6_32013-02-20redhat
redhatjava-1.7.0-openjdk-1:1.7.0.9-2.3.7.1.el6_32013-02-20redhat

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

(19)

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 2× in last 7d / 27× 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 09:59 UTCOSV refresh
  2. 2026-07-01 15:02 UTCEPSS rescore
  3. 2026-06-29 14:02 UTCEPSS rescore
  4. 2026-06-28 04:53 UTCEPSS rescore
  5. 2026-06-28 04:53 UTCEPSS rescore
  6. 2026-06-27 03:05 UTCEPSS rescore
  7. 2026-06-25 13:46 UTCEPSS rescore
  8. 2026-06-24 14:02 UTCEPSS rescore
  9. 2026-06-24 14:02 UTCEPSS rescore
  10. 2026-06-23 21:30 UTCEPSS rescore
  11. 2026-06-21 01:57 UTCEPSS rescore
  12. 2026-06-21 01:56 UTCEPSS rescore
  13. 2026-06-18 17:49 UTCEPSS rescore
  14. 2026-06-18 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-17 17:49 UTCEPSS rescore
  17. 2026-06-16 21:05 UTCOSV refresh
  18. 2026-06-16 17:49 UTCEPSS rescore
  19. 2026-06-16 17:49 UTCEPSS rescore
  20. 2026-06-15 17:44 UTCEPSS rescore
  21. 2026-06-14 23:14 UTCEPSS rescore
  22. 2026-06-13 22:57 UTCEPSS rescore
  23. 2026-06-12 23:08 UTCEPSS rescore
  24. 2026-06-11 13:56 UTCEPSS rescore
  25. 2026-06-10 13:18 UTCEPSS rescore
Show 42 more
  1. 2026-06-08 14:14 UTCEPSS rescore
  2. 2026-06-07 15:22 UTCEPSS rescore
  3. 2026-06-06 13:45 UTCEPSS rescore
  4. 2026-06-06 13:45 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-29 01:02 UTCEG score recompute
  20. 2026-05-29 01:02 UTCVendor advisory
  21. 2026-05-29 01:02 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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCwearohat/lucky13
    First seen Apr 1, 2025

    Exploit for cve-2013-0169

    Open source ↗

Frequently asked(4)

What is CVE-2013-0169?
CVE-2013-0169 is a none vulnerability published on February 8, 2013. The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct…
When was CVE-2013-0169 disclosed?
CVE-2013-0169 was first published in the National Vulnerability Database on February 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-0169 actively exploited?
CVE-2013-0169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-0169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-0169, 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-0169

Explore →

Is Your Infrastructure Affected by CVE-2013-0169?

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

Start Free Scan →Browse All CVEs