CVE-1999-0513

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 70.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
Weaponized
5.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 70%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 70%CVSS v2: 5.0Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ICMP messages to broadcast addresses are allowed, allowing for a Smurf attack that can cause a denial of service.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0(low)
EG Risk
55(Track)
EG Risk 55/100SSVC: Track

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%
Exploitation70% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
70%
EPSS %ILE
99%
KEV
Not listed

Published

January 5, 1998

Last Modified

June 16, 2026

References (2)

Data Freshness Timeline

(refreshed 6× in last 7d / 13× 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-26 13:19 UTCEG score recompute▲ 5.00
  2. 2026-07-23 00:40 UTCEG score recompute
  3. 2026-07-23 00:23 UTCEG score recompute▼ 6.60
  4. 2026-07-22 23:45 UTCEG score recompute▲ 6.60
  5. 2026-07-22 21:25 UTCEG score recompute
  6. 2026-07-20 17:02 UTCEPSS rescore
  7. 2026-07-16 16:58 UTCEPSS rescore
  8. 2026-07-15 16:53 UTCEPSS rescore
  9. 2026-07-15 01:55 UTCEPSS rescore
  10. 2026-07-08 15:08 UTCEPSS rescore
  11. 2026-07-04 06:26 UTCEPSS rescore
  12. 2026-07-02 14:00 UTCEPSS rescore
  13. 2026-06-29 14:02 UTCEPSS rescore
  14. 2026-06-24 14:01 UTCEPSS rescore
  15. 2026-06-23 21:29 UTCEPSS rescore
  16. 2026-06-21 01:56 UTCEPSS rescore
  17. 2026-06-17 17:49 UTCEPSS rescore
  18. 2026-06-14 23:13 UTCEPSS rescore
  19. 2026-06-13 22:56 UTCEPSS rescore
  20. 2026-06-12 23:07 UTCEPSS rescore
  21. 2026-06-11 13:55 UTCEPSS rescore
  22. 2026-06-10 22:13 UTCEPSS rescore
  23. 2026-06-10 13:17 UTCEPSS rescore
  24. 2026-06-06 13:44 UTCEPSS rescore
  25. 2026-06-05 06:07 UTCEPSS rescore
Show 25 more
  1. 2026-06-04 13:09 UTCEPSS rescore
  2. 2026-06-02 20:10 UTCEPSS rescore
  3. 2026-06-01 13:48 UTCEPSS rescore
  4. 2026-05-31 22:56 UTCEG score recompute
  5. 2026-05-31 22:56 UTCGHSA enrichment
  6. 2026-05-31 00:13 UTCEPSS rescore
  7. 2026-05-31 00:13 UTCEPSS rescore
  8. 2026-05-29 13:40 UTCEPSS rescore
  9. 2026-05-28 13:42 UTCEPSS rescore
  10. 2026-05-28 13:42 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-27 13:37 UTCEPSS rescore
  14. 2026-05-27 13:37 UTCEPSS rescore
  15. 2026-05-26 13:41 UTCEPSS rescore
  16. 2026-05-26 13:41 UTCEPSS rescore
  17. 2026-05-26 13:41 UTCEPSS rescore
  18. 2026-05-24 16:42 UTCEPSS rescore
  19. 2026-05-22 21:15 UTCEPSS rescore
  20. 2026-05-21 22:38 UTCEPSS rescore
  21. 2026-05-20 22:36 UTCEPSS rescore
  22. 2026-05-20 11:20 UTCEPSS rescore
  23. 2026-05-20 11:20 UTCEPSS rescore
  24. 2026-05-18 21:29 UTCEPSS rescore
  25. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-19117✓ verified
    First seen Jan 5, 1998

    Linux Kernel 2.0/2.1 (Digital UNIX 4.0 D / FreeBSD 2.2.4 / HP HP-UX 10.20/11.0 / IBM AIX 3.2.5 / NetBSD 1.2 / Solaris 2.5.1) - Smurf Denial of Service

    Open source ↗

Frequently asked(4)

What is CVE-1999-0513?
CVE-1999-0513 is a medium vulnerability published on January 5, 1998. ICMP messages to broadcast addresses are allowed, allowing for a Smurf attack that can cause a denial of service.
When was CVE-1999-0513 disclosed?
CVE-1999-0513 was first published in the National Vulnerability Database on January 5, 1998, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-1999-0513 actively exploited?
CVE-1999-0513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 70% probability of exploitation in the next 30 days, which ranks it in the top 0.7% of all scored CVEs.
How do I remediate CVE-1999-0513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-1999-0513, 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-1999-0513

Explore →

Is Your Infrastructure Affected by CVE-1999-0513?

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

Start Free Scan →Browse All CVEs