LiveActive security incident?Get immediate response
CVE Record

CVE-2008-3843: Request Validation (aka the ValidateRequest filters) in ASP.NET in Microsoft .NET Framework with the MS07-0...

Request Validation (aka the ValidateRequest filters) in ASP.NET in Microsoft .NET Framework with the MS07-040 update does not properly detect dangerous client input, which allows remote attackers to conduct cross-site scripting (XSS) attacks, as demonstrated by a query string containing a "<~/" (less-than tilde slash) sequence followed by a crafted STYLE element.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue is an old ASP.NET cross-site scripting weakness. Microsoft .NET Framework request validation could miss dangerous input, so an attacker might get script-like content reflected through a vulnerable web application. Business impact depends on whether legacy ASP.NET applications still rely on this filter as their main XSS defense. Exposure is most plausible in legacy ASP.NET applications using affected Microsoft .NET Framework behavior and relying on ValidateRequest to block malicious request data. The bundle does not provide exact supported versions, CPEs, or a complete affected product matrix. Address during legacy web application risk reduction, with higher priority for internet-facing ASP.NET systems handling authenticated sessions or sensitive data. No active exploitation evidence is provided, but the weakness undermines a commonly trusted defensive filter. Mitigation focus: Check Microsoft or vendor guidance for applicable framework updates or configuration changes.; Do not rely on ValidateRequest as the only XSS control.; Review affected ASP.NET pages for context-aware output encoding..

Prepared

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-2008-3843 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
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
2Source links

CVSS and timeline data

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

Source materials

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.