CVE-2002-0391

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 58.1%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 58%
CISA-KEV: Not listedEPSS PROB: 58%CVSS: 9.8Exploit: Elevated riskExposed: 0

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.8(medium)
EG Risk
82(Track)
EG Risk 82/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
Severity98% × 45%
Exploitation58% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
58%
EPSS %ILE
99%
KEV
Not listed

Published

August 12, 2002

Last Modified

June 16, 2026

References (76)

Patch Availability(6)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
acm—5.0-10—
dietlibc—0.20-0cvs20020808—
glibc—2.2.5-13—
krb5—1.2.5-2—
openafs—1.2.6-1—
Debian:12(5)
PackageVulnerable rangeFixed inDependents
acm—5.0-10—
dietlibc—0.20-0cvs20020808—
glibc—2.2.5-13—
krb5—1.2.5-2—
openafs—1.2.6-1—
Debian:13(5)
PackageVulnerable rangeFixed inDependents
acm—5.0-10—
dietlibc—0.20-0cvs20020808—
glibc—2.2.5-13—
krb5—1.2.5-2—
openafs—1.2.6-1—
Debian:3.0(5)
PackageVulnerable rangeFixed inDependents
acm—5.0-3.woody.1—
dietlibc—0.12-2.4—
glibc—2.2.5-11.1—
krb5—1.2.4-5woody1—
openafs—1.2.3final2-6—
Debian:14(3)
PackageVulnerable rangeFixed inDependents
dietlibc—0.20-0cvs20020808—
glibc—2.2.5-13—
krb5—1.2.5-2—

Weakness Classification(1)

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

All Vendor Advisories

(6)

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 1× in last 7d / 3× 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-08-26 13:43 UTCOSV refresh
  2. 2026-08-10 02:40 UTCOSV refresh
  3. 2026-08-03 10:27 UTCEPSS rescore
  4. 2026-07-25 03:11 UTCOSV refresh
  5. 2026-07-23 00:44 UTCEG score recompute
  6. 2026-07-23 00:25 UTCEG score recompute
  7. 2026-07-22 23:48 UTCEG score recompute
  8. 2026-07-22 21:28 UTCEG score recompute
  9. 2026-07-20 17:02 UTCEPSS rescore
  10. 2026-07-18 09:59 UTCEPSS rescore
  11. 2026-07-16 16:58 UTCEPSS rescore
  12. 2026-07-15 16:53 UTCEPSS rescore
  13. 2026-07-13 06:07 UTCEPSS rescore
  14. 2026-07-11 08:22 UTCEPSS rescore
  15. 2026-07-08 15:08 UTCEPSS rescore
  16. 2026-07-07 21:42 UTCOSV refresh
  17. 2026-07-02 14:00 UTCEPSS rescore
  18. 2026-06-27 03:04 UTCEPSS rescore
  19. 2026-06-23 21:29 UTCEPSS rescore
  20. 2026-06-22 14:22 UTCEPSS rescore
  21. 2026-06-21 01:56 UTCEPSS rescore
  22. 2026-06-19 19:22 UTCEPSS rescore
  23. 2026-06-19 09:25 UTCOSV refresh
  24. 2026-06-18 17:49 UTCEPSS rescore
  25. 2026-06-18 17:49 UTCEPSS rescore
Show 55 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-13 22:56 UTCEPSS rescore
  4. 2026-06-12 23:07 UTCEPSS rescore
  5. 2026-06-11 13:55 UTCEPSS rescore
  6. 2026-06-10 22:13 UTCEPSS rescore
  7. 2026-06-10 13:17 UTCEPSS rescore
  8. 2026-06-08 14:13 UTCEPSS rescore
  9. 2026-06-07 15:21 UTCEPSS rescore
  10. 2026-06-06 13:44 UTCEPSS rescore
  11. 2026-06-05 06:07 UTCEPSS rescore
  12. 2026-06-04 13:09 UTCEPSS rescore
  13. 2026-06-02 20:10 UTCEPSS rescore
  14. 2026-06-01 13:48 UTCEPSS rescore
  15. 2026-05-31 22:27 UTCEPSS rescore
  16. 2026-05-31 00:13 UTCEPSS rescore
  17. 2026-05-31 00:13 UTCEPSS rescore
  18. 2026-05-30 18:53 UTCOSV refresh
  19. 2026-05-29 13:40 UTCEPSS rescore
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-28 13:42 UTCEPSS rescore
  24. 2026-05-27 13:37 UTCEPSS rescore
  25. 2026-05-27 13:37 UTCEPSS rescore
  26. 2026-05-26 13:41 UTCEPSS rescore
  27. 2026-05-26 13:41 UTCEPSS rescore
  28. 2026-05-26 13:41 UTCEPSS rescore
  29. 2026-05-26 07:16 UTCEPSS rescore
  30. 2026-05-26 07:16 UTCEPSS rescore
  31. 2026-05-24 16:42 UTCEPSS rescore
  32. 2026-05-22 21:15 UTCEPSS rescore
  33. 2026-05-21 22:38 UTCEPSS rescore
  34. 2026-05-20 22:36 UTCEPSS rescore
  35. 2026-05-20 11:20 UTCEPSS rescore
  36. 2026-05-20 11:20 UTCEPSS rescore
  37. 2026-05-20 07:48 UTCVendor advisory
  38. 2026-05-20 07:48 UTCGHSA enrichment
  39. 2026-05-20 03:35 UTCVendor advisory
  40. 2026-05-20 03:35 UTCGHSA enrichment
  41. 2026-05-19 23:20 UTCVendor advisory
  42. 2026-05-19 23:20 UTCGHSA enrichment
  43. 2026-05-19 19:09 UTCVendor advisory
  44. 2026-05-19 19:09 UTCGHSA enrichment
  45. 2026-05-19 14:53 UTCVendor advisory
  46. 2026-05-19 14:53 UTCGHSA enrichment
  47. 2026-05-19 10:18 UTCVendor advisory
  48. 2026-05-19 10:18 UTCGHSA enrichment
  49. 2026-05-19 06:07 UTCVendor advisory
  50. 2026-05-19 06:07 UTCGHSA enrichment
  51. 2026-05-19 01:57 UTCEG score recompute
  52. 2026-05-19 01:57 UTCVendor advisory
  53. 2026-05-19 01:57 UTCGHSA enrichment
  54. 2026-05-18 21:29 UTCEPSS rescore
  55. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2002-0391?
CVE-2002-0391 is a critical vulnerability 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 disclosed?
CVE-2002-0391 was first published in the National Vulnerability Database on August 12, 2002, 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-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, which ranks it in the top 1.0% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-0391, 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

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.

Start Free Scan →Browse All CVEs