CVE-2004-2768

HIGHCVSS v2 · 7.27.2
EchelonGraph scoreLOW confidence

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

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.2 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:L/AC:L/Au:N/C:C/I:C/A:C. 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 0.4% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
7.2EG
EchelonGraph verdictPlan a fixRemediate 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 v2: 7.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

dpkg 1.9.21 does not properly reset the metadata of a file during replacement of the file in a package upgrade, which might allow local users to gain privileges by creating a hard link to a vulnerable (1) setuid file, (2) setgid file, or (3) device, a related issue to CVE-2010-2059.

CVSS v2.0 (legacy)
7.2HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.2HIGHlow confidence
EG Risk
33
EG Risk 33/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)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.
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).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

June 8, 2010

Last Modified

April 29, 2026

References (5)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
dpkg—
  • every version up to 1.10.19: fixed in 1.10.19
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
dpkg—
  • every version up to 1.10.19: fixed in 1.10.19
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
dpkg—
  • every version up to 1.10.19: fixed in 1.10.19
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
dpkg—
  • every version up to 1.10.19: fixed in 1.10.19
—

Data Freshness Timeline

(refreshed 8× in last 7d / 16× 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 77 of 88 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. 23 repeat rows among the latest 100 are merged into the row they repeat. The 11 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 02:21 UTCEG score recompute
  2. 2026-10-11 13:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-10 19:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-09 19:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-08 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-07 23:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-06 15:08 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-05 17:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-04 23:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-01 19:41 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-01 19:40 UTCOSV refresh
  12. 2026-09-29 02:42 UTCEG score recompute
  13. 2026-09-18 19:20 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-09-17 19:20 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-09-12 14:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-09-12 14:40 UTCOSV refresh
  17. 2026-09-10 09:23 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-09-04 04:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-08-24 20:02 UTCOSV refresh
  20. 2026-08-08 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-08-08 13:19 UTCOSV refresh
  22. 2026-08-05 19:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-07-26 13:25 UTCEG score recomputeFirst assessed: 7.2 HIGH
  24. 2026-07-25 14:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-07-24 14:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 52 more
  1. 2026-07-23 06:19 UTCOSV refresh
  2. 2026-07-23 00:47 UTCEG score recompute
  3. 2026-07-23 00:27 UTCEG score recompute
  4. 2026-07-22 23:51 UTCEG score recompute
  5. 2026-07-22 21:31 UTCEG score recompute
  6. 2026-07-18 09:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-07-15 16:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-07-15 01:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-07-13 22:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-07-13 06:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-07-11 08:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-07-08 15:09 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-07-06 02:19 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-07-06 01:29 UTCOSV refresh
  15. 2026-07-02 14:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-07-01 15:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-06-29 14:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-06-28 04:52 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-06-27 03:04 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-06-25 13:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-06-24 14:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-06-23 21:29 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-06-22 14:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-06-21 01:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-06-19 19:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  26. 2026-06-18 17:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  27. 2026-06-17 17:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  28. 2026-06-17 12:35 UTCOSV refresh
  29. 2026-06-16 17:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  30. 2026-06-15 17:44 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  31. 2026-06-14 23:13 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  32. 2026-06-13 22:56 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  33. 2026-06-12 23:08 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  34. 2026-06-11 13:55 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  35. 2026-06-10 22:14 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  36. 2026-06-10 13:17 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  37. 2026-06-08 14:13 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  38. 2026-06-07 15:21 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  39. 2026-06-06 13:44 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  40. 2026-06-05 22:43 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  41. 2026-06-05 06:07 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  42. 2026-06-04 13:09 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  43. 2026-06-02 20:10 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  44. 2026-06-01 13:49 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  45. 2026-05-31 22:28 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  46. 2026-05-31 00:13 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  47. 2026-05-29 13:40 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  48. 2026-05-29 11:24 UTCEG score recompute
  49. 2026-05-29 11:24 UTCGHSA enrichmentGHSA-qrp8-65v4-pc63 · GitHub severity HIGH
  50. 2026-05-28 13:42 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  51. 2026-05-27 13:37 UTCEPSS rescoreEPSS <0.1% · 19th percentile
  52. 2026-05-26 13:41 UTCEPSS rescoreEPSS <0.1% · 19th percentile

Related CVEs(same product)

Frequently asked(4)

What is CVE-2004-2768?
CVE-2004-2768 is a high-severity vulnerability; its CVE record was published on June 8, 2010. dpkg 1.9.21 does not properly reset the metadata of a file during replacement of the file in a package upgrade, which might allow local users to gain privileges by creating a hard link to a vulnerable (1) setuid file, (2) setgid file, or (3) device, a related issue to CVE-2010-2059.
When was CVE-2004-2768 made public?
CVE-2004-2768 was made public on March 8, 2004: 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 June 8, 2010. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2004-2768 actively exploited?
CVE-2004-2768 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).
How do I remediate CVE-2004-2768?
A fix for CVE-2004-2768 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-2004-2768

Explore →

Is Your Infrastructure Affected by CVE-2004-2768?

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

Book a Demo →Browse All CVEs