CVE-1999-0084

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
8.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.4Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 1990 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

CISA-ADP, in the CVE record, lists sun nfs versions before 4.1.3 as affected. No release containing a fix is confirmed on record.

Certain NFS servers allow users to use mknod to gain privileges by creating a writable kmem device and setting the UID to 0.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

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 (value × EchelonGraph’s weight)
Severity84% × 45%
The EG Score, 8.4 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 1990. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 1990. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 1, 1990

Last Modified

June 16, 2026

Advisory Details (1)

Auto-updated Jun 19, 2026
No fix on record since 1990.
Web page

IBM X-Force Exchange

https://exchange.xforce.ibmcloud.com/vulnerabilities/78

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 13× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 78 are merged into the row they repeat.

  1. 2026-10-13 16:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-12 22:26 UTCEG score recompute
  3. 2026-10-12 16:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-12 02:32 UTCEG score recompute
  5. 2026-10-11 13:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-10 19:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-09 19:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-08 16:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-07 23:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-06 15:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-05 17:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-04 23:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-09-29 02:27 UTCEG score recompute
  14. 2026-09-04 04:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-08-03 10:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-07-23 00:40 UTCEG score recompute
  17. 2026-07-23 00:22 UTCEG score recompute
  18. 2026-07-22 23:45 UTCEG score recompute
  19. 2026-07-22 21:24 UTCEG score recompute
  20. 2026-07-20 17:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-07-18 09:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-07-16 16:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-07-15 16:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-07-15 01:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-07-13 06:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 42 more
  1. 2026-07-11 08:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-07-04 06:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-07-02 14:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-06-29 14:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-06-28 14:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-06-27 03:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-06-24 14:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-06-23 21:29 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-06-22 14:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-06-21 01:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-06-19 19:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-06-18 17:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-06-17 17:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-06-16 17:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-06-14 23:13 UTCEPSS rescoreEPSS 0.1% · 35th percentile
  16. 2026-06-13 22:56 UTCEPSS rescoreEPSS 0.1% · 35th percentile
  17. 2026-06-12 23:07 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  18. 2026-06-11 13:55 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  19. 2026-06-10 22:13 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  20. 2026-06-10 13:17 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  21. 2026-06-08 14:13 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  22. 2026-06-07 15:21 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  23. 2026-06-06 13:44 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  24. 2026-06-05 06:07 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  25. 2026-06-04 13:09 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  26. 2026-06-02 20:10 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  27. 2026-06-01 13:48 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  28. 2026-05-31 23:17 UTCEG score recompute
  29. 2026-05-31 23:17 UTCGHSA enrichmentGHSA-v3vm-mf33-hv7v · GitHub severity HIGH · GitHub CVSS 8.4
  30. 2026-05-31 22:27 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  31. 2026-05-31 00:13 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  32. 2026-05-29 13:40 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  33. 2026-05-28 13:42 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  34. 2026-05-27 13:37 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  35. 2026-05-26 13:41 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  36. 2026-05-26 07:16 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  37. 2026-05-24 16:42 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  38. 2026-05-22 21:15 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  39. 2026-05-21 22:38 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  40. 2026-05-20 22:36 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  41. 2026-05-20 11:20 UTCEPSS rescoreEPSS 0.1% · 34th percentile
  42. 2026-05-18 21:29 UTCEPSS rescoreEPSS 0.1% · 34th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-1999-0084?
CVE-1999-0084 is a high-severity vulnerability; its CVE record was published on May 1, 1990. Certain NFS servers allow users to use mknod to gain privileges by creating a writable kmem device and setting the UID to 0.
When was the CVE record for CVE-1999-0084 published?
The CVE record for CVE-1999-0084 was published on May 1, 1990. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 16, 2026; the record at its source may have been updated since.
Is CVE-1999-0084 actively exploited?
CVE-1999-0084 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-1999-0084?
CVE-1999-0084 has a CVSS v3.1 base score of 8.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-1999-0084?
No fix for CVE-1999-0084 has been recorded since its CVE record was published in 1990. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product. CISA-ADP, in the CVE record, lists sun nfs versions before 4.1.3 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-1999-0084

Explore →

Is Your Infrastructure Affected by CVE-1999-0084?

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

Book a Demo →Browse All CVEs