CVE-1999-0861 microsoft: Race Condition
microsoft: no CVSS score yet. EPSS 3.2% estimated probability of exploitation activity in the next 30 days.
Race condition in the SSL ISAPI filter in IIS and other servers may leak information in plaintext.
- EPSS
- 3.2% (unchanged from 3.2% a week ago; 3.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 88th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
- OWASP Top 10
- A06:2025 Insecure Design
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-1999-0861 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-1999-0861?via=ask-ai-copy and https://cve.bz/cve/CVE-1999-0861?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-1999-0861 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
- microsoft:commercial_internet_system
- microsoft:internet_information_server
- microsoft:site_server
- microsoft:site_server_commerce
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| microsoft:commercial_internet_system | 2.0 |
| microsoft:commercial_internet_system | 2.5 |
| microsoft:internet_information_server | 4.0 |
| microsoft:site_server | 3.0 |
| microsoft:site_server_commerce | 3.0 |
Attack patterns (CAPEC)
- CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
- CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.