dbcve.org
.net FrameworkApplication · Microsoft

CVE-2007-0041

HIGH · 9.3 CVSS v2.0 Published 2007-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The PE Loader service in Microsoft .NET Framework 1.0, 1.1, and 2.0 for Windows 2000, XP, Server 2003, and Vista allows remote attackers to execute arbitrary code via unspecified vectors involving an "unchecked buffer" and unvalidated message lengths, probably a buffer overflow.

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 · moderate confidence

Buffer overflow vulnerability in the PE Loader service of Microsoft .NET Framework 1.0, 1.1, and 2.0 allows remote attackers to execute arbitrary code via unchecked buffers and unvalidated message lengths when processing PE (Portable Executable) files.

MitigationApply Microsoft security updates for the affected .NET Framework versions on Windows 2000, XP, Server 2003, and Vista; prioritize systems exposed to untrusted network inputs.

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
.net FrameworkApplication
Affected:= 1.0= 1.1= 2.0

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed .NET Framework version
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP, or run 'reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP" /s' from command prompt
    Affected if The displayed version matches 1.0, 1.1, or 2.0 exactly
  2. Confirm full version number
    Under the identified NDP key (e.g., v1.0, v1.1, or v2.0), check the 'Version' string value in the right pane
    Affected if Version is exactly 1.0, 1.1, or 2.0 (or falls within these specific version families)
  3. Verify PE Loader component presence
    Check for the presence of mscoree.dll or mscorwks.dll in the .NET Framework installation directory (typically C:\Windows\Microsoft.NET\Framework\vX.X.X\)
    Affected if These DLLs exist and are from affected .NET Framework versions 1.0-2.0
  4. Confirm Windows version is vulnerable OS
    Run 'winver' or check system properties to identify Windows version
    Affected if Operating system is Windows 2000, XP, Server 2003, or Vista as listed in affected platforms
  5. Audit .NET Framework installations across system
    Run 'wmic product list' or check Add/Remove Programs for multiple .NET Framework installations
    Affected if Any installed instance is version 1.0, 1.1, or 2.0

The environment is affected if any installed instance of Microsoft .NET Framework matches versions 1.0, 1.1, or 2.0 on Windows 2000, XP, Server 2003, or Vista, as these versions contain the vulnerable PE Loader service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for the affected .NET Framework versions on Windows 2000, XP, Server 2003, and Vista; prioritize systems exposed to untrusted network inputs.

Recommended fix Moderate confidence

Microsoft no longer supports .NET Framework 1.0/1.1/2.0; upgrade to a supported version such as .NET Framework 4.8 or .NET 6/7 (if migrating to modern .NET)

  1. Apply Microsoft Security Bulletin MS07-040, which addresses this vulnerability in .NET Framework
  2. For .NET Framework 1.0: Ensure KB928366 is installed or apply .NET Framework 1.0 Service Pack 3
  3. For .NET Framework 1.1: Ensure KB928367 is installed or apply .NET Framework 1.1 Service Pack 1
  4. For .NET Framework 2.0: Ensure KB928368 is installed or apply .NET Framework 2.0 Service Pack 1
  5. After applying patches, verify through Windows Update that no further .NET Framework updates are pending
  6. Restart the system if prompted to complete the installation
Caveat Patches for end-of-life .NET Framework versions may have limited support; upgrading to newer .NET versions may require code changes due to API differences

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in .net Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0041 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0041 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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