CVE-1999-1332

LOWCVSS v2 · 2.12.1—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 2.1 — v2 rates that LOW (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:L/Au:N/C:N/I:P/A:N. 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, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS v2: 2.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.

gzexe in the gzip package on Red Hat Linux 5.0 and earlier allows local users to overwrite files of other users via a symlink attack on a temporary file.

CVSS v2.0 (legacy)
2.1LOWNVD never assigned a CVSS v3 rating to this CVE
EG Score
2.1LOWlow confidence
EG Risk
14
EG Risk 14/100CISA SSVC

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
Severity21% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
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.4%
EPSS %ILE
31st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or 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 unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 31, 1999

Last Modified

June 16, 2026

References (12)

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
gzip—1.3.5-6—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
gzip—1.3.5-6—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gzip—1.3.5-6—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
gzip—1.3.5-6—
Debian:3.0(1)
PackageVulnerable rangeFixed inDependents
gzip—1.3.2-3woody1—

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

Related CVEs(same product)

Frequently asked(4)

What is CVE-1999-1332?
CVE-1999-1332 is a low vulnerability published on December 31, 1999. gzexe in the gzip package on Red Hat Linux 5.0 and earlier allows local users to overwrite files of other users via a symlink attack on a temporary file.
When was CVE-1999-1332 disclosed?
CVE-1999-1332 was first published on December 31, 1999, 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-1999-1332 actively exploited?
CVE-1999-1332 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
How do I remediate CVE-1999-1332?
No fix for CVE-1999-1332 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-1999-1332

Explore →

Is Your Infrastructure Affected by CVE-1999-1332?

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

Book a Demo →Browse All CVEs