CVE-1999-0233
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 1.0 allows users to execute arbitrary commands using .bat or .cmd files.
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 1.0 contains a command injection vulnerability allowing remote attackers to execute arbitrary operating system commands through .bat or .cmd files. The vulnerability stems from insufficient input validation when IIS processes batch file requests, enabling attackers to inject shell commands that execute with the privileges of the web server process.
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= 1.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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 if IIS is installed and runningCheck the Windows Services list for 'IIS' or 'World Wide Web Publishing Service', or check if port 80 is listening using 'netstat -an | findstr :80'Affected if IIS is not installed or not running means not affected
-
Confirm the exact IIS versionCheck the IIS version via the IIS Manager snap-in, the registry key HKLM\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\MajorVersion, or by requesting a file from the web server and inspecting response headersAffected if The version must be exactly 1.0 to be affected; later versions are not vulnerable to this specific CVE
-
Identify if .bat and .cmd handler mappings are enabledOpen IIS Manager, navigate to the website or application, go to Handler Mappings, and look for entries named 'Batch' or 'CMD' or scripts mapped to .bat/.cmd extensionsAffected if If .bat/.cmd handler mappings exist and are enabled, the command injection vector is present
-
Check executable permissions on web content directoriesIn IIS Manager, right-click the root website folder, select Permissions, or check the script permission setting under Home Directory in the website propertiesAffected if If Execute Permissions are set to 'Scripts and Executables' or 'Executables' in any web-accessible directory, arbitrary command execution is possible
The environment is affected only if IIS version 1.0 is running with .bat/.cmd handler mappings enabled and executable permissions granted to web directories.
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 dataUpgrade from IIS 1.0 to a supported IIS version with current security patches, or decommission the legacy system. If continued operation is required, disable .bat and .cmd handler mappings and restrict executable permissions to prevent command execution via the web server.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0233 — 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-1999-0233 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