CVE-1999-0517

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2022-04-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Weaponized
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 27%CVSS: 5.9Exploit: NoneExposed: 0

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

An SNMP community name is the default (e.g. public), null, or missing.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
—
EPSS
97.8%
KEV
Not listed

Published

January 1, 1997

Last Modified

June 16, 2026

Advisory Details (3)

Auto-updated Jun 19, 2026
No patch confirmed yet.
generic

Support Content Notification - Support Portal - Broadcom support portal

https://www.broadcom.com/support/fibre-channel-networking/security-advisories/brocade-security-advisory-2017-244/
generic

Support Content Notification - Support Portal - Broadcom support portal

https://www.broadcom.com/support/fibre-channel-networking/security-advisories/brocade-security-advisory-2017-244
generic

IBM X-Force Exchange

https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0517

Vendor Advisories for CVE-1999-0517(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • Metasploitauxiliary/scanner/snmp/snmp_login✓ verified
    First seen Jan 1, 1999

    SNMP Community Login Scanner

    Open source ↗
  • Metasploitauxiliary/scanner/snmp/snmp_enum✓ verified
    First seen Jan 1, 1999

    SNMP Enumeration Module

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-1999-0517?
CVE-1999-0517 is a medium vulnerability published on January 1, 1997. An SNMP community name is the default (e.g. public), null, or missing.
When was CVE-1999-0517 disclosed?
CVE-1999-0517 was first published in the National Vulnerability Database on January 1, 1997, 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-0517 actively exploited?
CVE-1999-0517 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-1999-0517?
CVE-1999-0517 has a CVSS v3.1 base score of 5.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-1999-0517?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-1999-0517, 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-0517

Explore →

Is Your Infrastructure Affected by CVE-1999-0517?

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

Start Free Scan →Browse All CVEs