CVE-2000-0226
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 allows attackers to cause a denial of service by requesting a large buffer in a POST or PUT command which consumes memory, aka the "Chunked Transfer Encoding Buffer Overflow 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 contains a vulnerability where specially crafted POST or PUT requests with large buffers in chunked transfer encoding consume excessive server memory, leading to denial of service. This is a resource exhaustion issue rather than traditional buffer overflow code execution.
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.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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Verify IIS is installedCheck for the presence of IIS by looking for the W3SVC service or IIS admin service in Windows Services (services.msc), or check for IIS installation directories under C:\Inetpub or C:\Winnt\System32\InetsrvAffected if IIS is not installed or not running, the vulnerability does not apply
-
Check IIS version numberRun 'iisver' from the IIS resource kit tools, or check the version property of the IISADMIN service executable at C:\Winnt\System32\Inetsrv\Iisadmin.dll, or query the registry key HKLM\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\MajorVersionAffected if The MajorVersion equals 4 (decimal) indicating IIS 4.0, meaning the system is vulnerable
-
Confirm Windows NT 4.0 platformRun 'winver' or check system properties to verify the operating system is Windows NT 4.0 with Option Pack installed, which shipped IIS 4.0Affected if Running Windows NT 4.0 Server with Option Pack, the environment contains the affected IIS 4.0 version
-
Verify WWW service is enabledCheck if the World Wide Web Publishing Service (W3SVC) is running via services.msc or command 'net start' outputAffected if The W3SVC service is running and accepting HTTP requests, making the chunked transfer encoding memory exhaustion flaw exploitable
If the system is running IIS version 4.0 (MajorVersion = 4) on Windows NT 4.0 with the WWW service active, the environment is affected by this CVE.
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 dataPatch IIS 4.0 or upgrade to a supported IIS version. If IIS 4.0 is still in use, migrate to current Windows Server with modern IIS as this is obsolete software.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0226 — 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-0226 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