CVE-2002-0391

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 58% (99th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 58%
CISA-KEV: Not listedEPSS PROB: 58%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Integer overflow in xdr_array function in RPC servers for operating systems that use libc, glibc, or other code based on SunRPC including dietlibc, allows remote attackers to execute arbitrary code by passing a large number of arguments to xdr_array through RPC services such as rpc.cmsd and dmispd.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
82
EG Risk 82/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation58% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: 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
58%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
58% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

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

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 12, 2002

Last Modified

June 16, 2026

References (38)

15 of 38 shown · show the other 23

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpatch2003-06-26redhat
redhatpatch2003-04-29redhat
redhatpatch2002-09-05redhat
redhatpatch2002-08-15redhat
redhatpatch2002-08-13redhat
redhatpatch2002-08-06redhat

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

(23 across 5 ecosystems)
Debian:11(5)
PackageVulnerable rangeFix by version rangeDependents
acm—
  • every version up to 5.0-10: fixed in 5.0-10
—
dietlibc—
  • every version up to 0.20-0cvs20020808: fixed in 0.20-0cvs20020808
—
glibc—
  • every version up to 2.2.5-13: fixed in 2.2.5-13
—
krb5—
  • every version up to 1.2.5-2: fixed in 1.2.5-2
—
openafs—
  • every version up to 1.2.6-1: fixed in 1.2.6-1
—
Debian:12(5)
PackageVulnerable rangeFix by version rangeDependents
acm—
  • every version up to 5.0-10: fixed in 5.0-10
—
dietlibc—
  • every version up to 0.20-0cvs20020808: fixed in 0.20-0cvs20020808
—
glibc—
  • every version up to 2.2.5-13: fixed in 2.2.5-13
—
krb5—
  • every version up to 1.2.5-2: fixed in 1.2.5-2
—
openafs—
  • every version up to 1.2.6-1: fixed in 1.2.6-1
—
Debian:13(5)
PackageVulnerable rangeFix by version rangeDependents
acm—
  • every version up to 5.0-10: fixed in 5.0-10
—
dietlibc—
  • every version up to 0.20-0cvs20020808: fixed in 0.20-0cvs20020808
—
glibc—
  • every version up to 2.2.5-13: fixed in 2.2.5-13
—
krb5—
  • every version up to 1.2.5-2: fixed in 1.2.5-2
—
openafs—
  • every version up to 1.2.6-1: fixed in 1.2.6-1
—
Debian:3.0(5)
PackageVulnerable rangeFix by version rangeDependents
acm—
  • every version up to 5.0-3.woody.1: fixed in 5.0-3.woody.1
—
dietlibc—
  • every version up to 0.12-2.4: fixed in 0.12-2.4
—
glibc—
  • every version up to 2.2.5-11.1: fixed in 2.2.5-11.1
—
krb5—
  • every version up to 1.2.4-5woody1: fixed in 1.2.4-5woody1
—
openafs—
  • every version up to 1.2.3final2-6: fixed in 1.2.3final2-6
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
dietlibc—
  • every version up to 0.20-0cvs20020808: fixed in 0.20-0cvs20020808
—
glibc—
  • every version up to 2.2.5-13: fixed in 2.2.5-13
—
krb5—
  • every version up to 1.2.5-2: fixed in 1.2.5-2
—

Weakness Classification(1)

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

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 27× in last 7d / 53× 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.

Showing the most recent 98 of 133 refreshes on record for this CVE.

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 35 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  2. 2026-10-23 05:32 UTCEG score recompute
  3. 2026-10-23 05:32 UTCVendor advisory
  4. 2026-10-23 05:32 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  5. 2026-10-22 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  6. 2026-10-22 05:44 UTCEG score recompute
  7. 2026-10-22 05:44 UTCVendor advisory
  8. 2026-10-22 05:44 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  9. 2026-10-21 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  10. 2026-10-21 05:56 UTCEG score recompute
  11. 2026-10-21 05:56 UTCVendor advisory
  12. 2026-10-21 05:55 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  13. 2026-10-20 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  14. 2026-10-20 06:09 UTCEG score recompute
  15. 2026-10-20 06:09 UTCVendor advisory
  16. 2026-10-20 06:08 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  17. 2026-10-19 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  18. 2026-10-19 06:21 UTCEG score recompute
  19. 2026-10-19 06:21 UTCVendor advisory
  20. 2026-10-19 06:21 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  21. 2026-10-18 06:33 UTCEG score recompute
  22. 2026-10-18 06:33 UTCVendor advisory
  23. 2026-10-18 06:32 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  24. 2026-10-17 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  25. 2026-10-17 06:43 UTCEG score recompute
Show 73 more
  1. 2026-10-17 06:43 UTCVendor advisory
  2. 2026-10-17 06:43 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  3. 2026-10-16 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  4. 2026-10-16 06:55 UTCEG score recompute
  5. 2026-10-16 06:55 UTCVendor advisory
  6. 2026-10-16 06:54 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  7. 2026-10-15 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  8. 2026-10-15 05:36 UTCEG score recompute
  9. 2026-10-15 05:36 UTCVendor advisory
  10. 2026-10-15 05:36 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  11. 2026-10-14 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  12. 2026-10-14 01:15 UTCEG score recompute
  13. 2026-10-14 01:15 UTCVendor advisory
  14. 2026-10-14 01:15 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  15. 2026-10-13 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  16. 2026-10-12 21:24 UTCEG score recompute
  17. 2026-10-12 21:24 UTCVendor advisory
  18. 2026-10-12 21:24 UTCGHSA enrichmentGHSA-2qf2-q2gj-r6v2 · GitHub severity HIGH
  19. 2026-10-12 16:24 UTCEPSS rescoreEPSS 58% · 99th percentile
  20. 2026-10-12 02:28 UTCEG score recompute
  21. 2026-10-11 13:36 UTCEPSS rescoreEPSS 58% · 99th percentile
  22. 2026-10-10 19:53 UTCEPSS rescoreEPSS 58% · 99th percentile
  23. 2026-10-09 19:58 UTCEPSS rescoreEPSS 58% · 99th percentile
  24. 2026-10-08 16:26 UTCEPSS rescoreEPSS 58% · 99th percentile
  25. 2026-10-07 23:35 UTCEPSS rescoreEPSS 58% · 99th percentile
  26. 2026-10-06 15:07 UTCEPSS rescoreEPSS 58% · 99th percentile
  27. 2026-10-03 22:58 UTCOSV refresh
  28. 2026-09-29 02:35 UTCEG score recompute
  29. 2026-09-14 12:44 UTCOSV refresh
  30. 2026-09-04 04:59 UTCEPSS rescoreEPSS 58% · 99th percentile
  31. 2026-08-26 13:43 UTCOSV refresh
  32. 2026-08-10 02:40 UTCOSV refresh
  33. 2026-08-03 10:27 UTCEPSS rescoreEPSS 58% · 98th percentile
  34. 2026-07-25 03:11 UTCOSV refresh
  35. 2026-07-23 00:44 UTCEG score recompute
  36. 2026-07-23 00:25 UTCEG score recompute
  37. 2026-07-22 23:48 UTCEG score recompute
  38. 2026-07-22 21:28 UTCEG score recompute
  39. 2026-07-20 17:02 UTCEPSS rescoreEPSS 58% · 98th percentile
  40. 2026-07-18 09:59 UTCEPSS rescoreEPSS 58% · 98th percentile
  41. 2026-07-16 16:58 UTCEPSS rescoreEPSS 58% · 98th percentile
  42. 2026-07-15 16:53 UTCEPSS rescoreEPSS 58% · 98th percentile
  43. 2026-07-13 06:07 UTCEPSS rescoreEPSS 58% · 98th percentile
  44. 2026-07-11 08:22 UTCEPSS rescoreEPSS 58% · 98th percentile
  45. 2026-07-08 15:08 UTCEPSS rescoreEPSS 58% · 98th percentile
  46. 2026-07-07 21:42 UTCOSV refresh
  47. 2026-07-02 14:00 UTCEPSS rescoreEPSS 58% · 98th percentile
  48. 2026-06-27 03:04 UTCEPSS rescoreEPSS 58% · 98th percentile
  49. 2026-06-23 21:29 UTCEPSS rescoreEPSS 58% · 98th percentile
  50. 2026-06-22 14:22 UTCEPSS rescoreEPSS 58% · 98th percentile
  51. 2026-06-21 01:56 UTCEPSS rescoreEPSS 58% · 98th percentile
  52. 2026-06-19 19:22 UTCEPSS rescoreEPSS 58% · 98th percentile
  53. 2026-06-19 09:25 UTCOSV refresh
  54. 2026-06-18 17:49 UTCEPSS rescoreEPSS 58% · 98th percentile
  55. 2026-06-17 17:49 UTCEPSS rescoreEPSS 58% · 98th percentile
  56. 2026-06-16 17:49 UTCEPSS rescoreEPSS 58% · 98th percentile
  57. 2026-06-13 22:56 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  58. 2026-06-12 23:07 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  59. 2026-06-11 13:55 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  60. 2026-06-10 22:13 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  61. 2026-06-10 13:17 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  62. 2026-06-08 14:13 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  63. 2026-06-07 15:21 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  64. 2026-06-06 13:44 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  65. 2026-06-05 06:07 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  66. 2026-06-04 13:09 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  67. 2026-06-02 20:10 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  68. 2026-06-01 13:48 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  69. 2026-05-31 22:27 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  70. 2026-05-31 00:13 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  71. 2026-05-30 18:53 UTCOSV refresh
  72. 2026-05-29 13:40 UTCEPSS rescoreEPSS 8.3% · 92nd percentile
  73. 2026-05-28 13:42 UTCEPSS rescoreEPSS 8.3% · 92nd percentile

Frequently asked(5)

What is CVE-2002-0391?
CVE-2002-0391 is a critical-severity vulnerability; its CVE record was published on August 12, 2002. Integer overflow in xdrarray function in RPC servers for operating systems that use libc, glibc, or other code based on SunRPC including dietlibc, allows remote attackers to execute arbitrary code by passing a large number of arguments to xdrarray through RPC services such as rpc.cmsd and dmispd.
When was CVE-2002-0391 made public?
CVE-2002-0391 was made public on July 29, 2002: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 12, 2002. 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-2002-0391 actively exploited?
CVE-2002-0391 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 58% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2002-0391?
CVE-2002-0391 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2002-0391?
A fix for CVE-2002-0391 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-2002-0391

Explore →

Is Your Infrastructure Affected by CVE-2002-0391?

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