CVE-2009-4444: n/a vulnerability

CVE-2009-4444: Microsoft Internet Information Services (IIS) 5.x and 6.x uses only the portion of a filename before a ; (s...

Microsoft Internet Information Services (IIS) 5.x and 6.x uses only the portion of a filename before a ; (semicolon) character to determine the file extension, which allows remote attackers to bypass intended extension restrictions of third-party upload applications via a filename with a (1) .asp, (2) .cer, or (3) .asa first extension, followed by a semicolon and a safe extension, as demonstrated by the use of asp.dll to handle a .asp;.jpg file.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 16, 2024, 18:12 UTC (UTC+00:00)

Security readout for executives and security teams

Legacy Microsoft IIS 5.x and 6.x can treat a filename differently than an upload application expects when a semicolon appears in the name. A file that looks safe to the application may still be handled as an executable script by IIS. The business risk is highest where old IIS servers accept user-uploaded files. Exposure is likely limited to legacy IIS 5.x or 6.x systems running upload functionality or third-party upload applications that rely on extension restrictions. Modern IIS versions are not identified in the provided bundle. Internet-facing upload endpoints increase concern, especially when uploads are stored under script-enabled directories. Prioritize this if the organization still operates legacy IIS upload services. The issue is old, but the impact can be serious because upload validation mistakes may allow server-side script handling. If no IIS 5.x or 6.x remains, urgency is low after verification. Mitigation focus: Inventory and retire or isolate IIS 5.x and 6.x systems.; Review Microsoft MSRC and application vendor guidance for supported fixes.; Reject semicolon-containing upload filenames before storage..

Prepared: Jun 28, 2026, 09:59 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2009-4444 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 29, 2009, 19:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.