CVE-2015-2153

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — v2 rates that MEDIUM (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:N/I:N/A:P. 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 19.0% 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
Trending — 3 sources updated this weekElevated
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 19%CVSS v2: 5.0Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

The rpki_rtr_pdu_print function in print-rpki-rtr.c in the TCP printer in tcpdump before 4.7.2 allows remote attackers to cause a denial of service (out-of-bounds read or write and crash) via a crafted header length in an RPKI-RTR Protocol Data Unit (PDU).

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0MEDIUMlow confidence
EG Risk
43
EG Risk 43/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
Severity50% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
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
19%
EPSS %ILE
97th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

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

Exploitation public PoC (EG-KEV: elevated) · 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

March 24, 2015

Last Modified

May 6, 2026

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutcpdump (4.6.2-1ubuntu1.2) @ utopic2026-05-28ubuntu
redhattcpdump-14:4.9.0-5.el72017-08-01redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
tcpdump—4.6.2-4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
tcpdump—4.6.2-4—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
tcpdump—4.6.2-4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
tcpdump—4.6.2-4—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
tcpdump4.3.0-1, 4.3.0-1+deb7u14.3.0-1+deb7u2—

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 18× 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 145 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

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

  • GitHub PoCarntsonl/CVE-2015-2153
    First seen Aug 27, 2015

    An implementation of the CVE-2015-2153 exploit.

    Open source ↗
  • Exploit-DBEDB-37663
    First seen Jul 20, 2015

    TcpDump - rpki_rtr_pdu_print Out-of-Bounds Denial of Service

    Open source ↗

Frequently asked(4)

What is CVE-2015-2153?
CVE-2015-2153 is a medium vulnerability published on March 24, 2015. The rpkirtrpdu_print function in print-rpki-rtr.c in the TCP printer in tcpdump before 4.7.2 allows remote attackers to cause a denial of service (out-of-bounds read or write and crash) via a crafted header length in an RPKI-RTR Protocol Data Unit (PDU).
When was CVE-2015-2153 disclosed?
CVE-2015-2153 was first published on March 24, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-2153 actively exploited?
CVE-2015-2153 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
How do I remediate CVE-2015-2153?
A fix for CVE-2015-2153 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-2153

Explore →

Is Your Infrastructure Affected by CVE-2015-2153?

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