Microsoft IIS
WebUsage: unknown. No public source measures this product yet.
Version split: unknown. No public source for this product.
Exploitation likely. EPSS gives it a 53% chance of exploitation in the next 30 days. No fix published yet.
No fixed build or workaround is published yet. Limit exposure and watch for a patch.
Buffer overflow in Internet Information Server (IIS) 4.0, 5.0, and 5.1 allows remote attackers to spoof the safety check for HTTP headers and cause a denial of service or execute arbitrary code via HTTP header field values.
This is an old flaw in very old Microsoft web server software (IIS 4.0/5.0/5.1) that could let an attacker crash the server or run code on it, but it's not being actively exploited and most businesses stopped using these versions decades ago.
Remote buffer overflow in IIS 4.0/5.0/5.1 lets an attacker spoof the HTTP header length-safety check, causing denial of service or potential arbitrary code execution via crafted header field values, with no exploitation confirmed and no fix information on record.
Where each signal puts this CVE on the scale from published to confirmed exploited.
Not in the catalog. CISA has not confirmed exploitation.
No public exploit or proof of concept found in the sources we track.
53% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Rising.
7 events over 8604 days, from the signal feeds we watch.
And 2 more affected products. See all after sign-in
How widely the affected products are used. This is not a count of vulnerable hosts.
Estimate Public sources, each figure dated. How much of it is already patched is not known.
Usage: unknown. No public source measures this product yet.
Version split: unknown. No public source for this product.
AV:N/AC:L/Au:N/C:P/I:P/A:P
Scored 7.5 by NVD.
And 6 more references. See all after sign-in
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory.