CVE-2000-0970

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. 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 43.5% 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
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 31%CVSS v2: 7.5Exploit: Elevated riskExposed: 0

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

IIS 4.0 and 5.0 .ASP pages send the same Session ID cookie for secure and insecure web sessions, which could allow remote attackers to hijack the secure web session of the user if that user moves to an insecure session, aka the "Session ID Cookie Marking" vulnerability.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5(low)
EG Risk
56(Track)
EG Risk 56/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
Severity75% × 45%
Exploitation44% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
31%
EPSS %ILE
98%
KEV
Not listed

Published

December 19, 2000

Last Modified

June 16, 2026

References (8)

Data Freshness Timeline

(refreshed 6× in last 7d / 14× 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-07-26 13:20 UTCEG score recompute▲ 7.50
  2. 2026-07-23 00:42 UTCEG score recompute
  3. 2026-07-23 00:24 UTCEG score recompute▼ 2.20
  4. 2026-07-22 23:47 UTCEG score recompute▲ 2.20
  5. 2026-07-22 21:27 UTCEG score recompute
  6. 2026-07-20 17:02 UTCEPSS rescore
  7. 2026-07-18 09:59 UTCEPSS rescore
  8. 2026-07-16 16:58 UTCEPSS rescore
  9. 2026-07-15 16:53 UTCEPSS rescore
  10. 2026-07-13 06:07 UTCEPSS rescore
  11. 2026-07-11 08:22 UTCEPSS rescore
  12. 2026-07-08 15:08 UTCEPSS rescore
  13. 2026-07-02 14:00 UTCEPSS rescore
  14. 2026-06-29 14:02 UTCEPSS rescore
  15. 2026-06-24 14:01 UTCEPSS rescore
  16. 2026-06-23 21:29 UTCEPSS rescore
  17. 2026-06-21 01:56 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-18 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-16 17:49 UTCEPSS rescore
  22. 2026-06-14 23:13 UTCEPSS rescore
  23. 2026-06-13 22:56 UTCEPSS rescore
  24. 2026-06-12 23:07 UTCEPSS rescore
  25. 2026-06-11 13:55 UTCEPSS rescore
Show 26 more
  1. 2026-06-10 22:13 UTCEPSS rescore
  2. 2026-06-10 13:17 UTCEPSS rescore
  3. 2026-06-07 15:21 UTCEPSS rescore
  4. 2026-06-06 13:44 UTCEPSS rescore
  5. 2026-06-05 06:07 UTCEPSS rescore
  6. 2026-06-04 13:09 UTCEPSS rescore
  7. 2026-06-02 20:10 UTCEPSS rescore
  8. 2026-05-31 22:27 UTCEPSS rescore
  9. 2026-05-31 21:13 UTCEG score recompute
  10. 2026-05-31 21:13 UTCGHSA enrichment
  11. 2026-05-31 00:13 UTCEPSS rescore
  12. 2026-05-31 00:13 UTCEPSS rescore
  13. 2026-05-29 13:40 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-27 13:37 UTCEPSS rescore
  19. 2026-05-27 13:37 UTCEPSS rescore
  20. 2026-05-24 16:42 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-20 22:36 UTCEPSS rescore
  23. 2026-05-20 11:20 UTCEPSS rescore
  24. 2026-05-20 11:20 UTCEPSS rescore
  25. 2026-05-18 21:29 UTCEPSS rescore
  26. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2000-0970?
CVE-2000-0970 is a high vulnerability published on December 19, 2000. IIS 4.0 and 5.0 .ASP pages send the same Session ID cookie for secure and insecure web sessions, which could allow remote attackers to hijack the secure web session of the user if that user moves to an insecure session, aka the "Session ID Cookie Marking" vulnerability.
When was CVE-2000-0970 disclosed?
CVE-2000-0970 was first published in the National Vulnerability Database on December 19, 2000, 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-2000-0970 actively exploited?
CVE-2000-0970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31% probability of exploitation in the next 30 days, which ranks it in the top 1.9% of all scored CVEs.
How do I remediate CVE-2000-0970?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2000-0970, 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

Explore the affected products and dependency analysis for CVE-2000-0970

Explore →

Is Your Infrastructure Affected by CVE-2000-0970?

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

Start Free Scan →Browse All CVEs