CVE-2005-2352

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2022-04-21. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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

I race condition in Temp files was found in gs-gpl before 8.56 addons scripts.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
41
EG Risk 41/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)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default: CISA has not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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

Published

November 1, 2019

Last Modified

November 20, 2024

Advisory Details (2)

Auto-updated Jul 13, 2026
No fix on record yet.
generic

CVE-2005-2352

https://security-tracker.debian.org/tracker/CVE-2005-2352
generic

[VIM] Old CVE ids, public, but still "RESERVED"

http://www.attrition.org/pipermail/vim/2014-February/002758.html

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 12× 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. 24 repeat rows among the latest 93 are merged into the row they repeat.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2005-2352?
CVE-2005-2352 is a high vulnerability published on November 1, 2019. I race condition in Temp files was found in gs-gpl before 8.56 addons scripts.
When was the CVE record for CVE-2005-2352 published?
The CVE record for CVE-2005-2352 was published on November 1, 2019. 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 November 20, 2024; the record at its source may have been updated since.
Is CVE-2005-2352 actively exploited?
CVE-2005-2352 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2005-2352?
CVE-2005-2352 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2005-2352?
No fix for CVE-2005-2352 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2005-2352

Explore →

Is Your Infrastructure Affected by CVE-2005-2352?

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

Book a Demo →Browse All CVEs