CVE-2000-0970
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIIS 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIIS 4.0 and 5.0 reuse the same Session ID cookie across both secure (HTTPS) and insecure (HTTP) sessions in ASP pages. This allows an attacker who can intercept or observe the Session ID from an insecure connection to hijack the user's subsequent secure session, as the server cannot distinguish between legitimate and stolen session credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.0= 5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify IIS versionCheck the installed IIS version by running 'iisreset /status' or checking the About dialog in the IIS Management Console, or inspect the metadata for the IIS serviceAffected if The installed version is Microsoft Internet Information Server 4.0 or Microsoft Internet Information Services 5.0
-
Confirm ASP Session State is enabledOpen IIS Management Console, navigate to the default website or affected application, right-click and select Properties, then check the 'Enable session state' checkbox under the ASP configuration options, or inspect the metabase for AspSessionTimeoutAffected if ASP session state is enabled and using in-process session management
-
Verify both HTTP and HTTPS are enabledCheck IIS manager for both the default website (HTTP on port 80) and a site bound to HTTPS on port 443, or run 'cscript adsutil.vbs get w3svc/1/ServerBindings' for each siteAffected if The server is configured to accept both HTTP and HTTPS connections on the same or different sites
-
Test Session ID reuse between protocolsEstablish an ASP session over HTTP, capture the SessionID cookie value using browser developer tools or a network trace, then make a request over HTTPS to the same ASP application and compare whether the SessionID remains identicalAffected if The same SessionID cookie value is returned and accepted for both HTTP and HTTPS requests to ASP pages
If the server runs IIS 4.0 or 5.0 with ASP session state enabled and accepts both HTTP and HTTPS connections, the SessionID cookie is likely being reused across both protocols, making users vulnerable to session hijacking.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement separate session management for secure and insecure contexts, either by configuring IIS to issue distinct Session ID cookies for HTTPS requests or by implementing application-level session token handling that differs between secure and non-secure paths.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0970 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2000-0970 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data