dbcve.org
.net FrameworkApplication · Microsoft

CVE-2007-0043

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 Just In Time (JIT) Compiler service in Microsoft .NET Framework 1.0, 1.1, and 2.0 for Windows 2000, XP, Server 2003, and Vista allows user-assisted remote attackers to execute arbitrary code via unspecified vectors involving an "unchecked buffer," probably a buffer overflow, aka ".NET JIT Compiler Vulnerability".

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

Buffer overflow vulnerability in the Just-In-Time (JIT) Compiler service of Microsoft .NET Framework 1.0, 1.1, and 2.0 allows remote attackers to execute arbitrary code via unspecified vectors involving an unchecked buffer. This affects Windows 2000, XP, Server 2003, and Vista.

MitigationApply Microsoft security patches for the .NET JIT Compiler vulnerability (MS07-029) to affected .NET Framework versions on all supported Windows systems.

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. Check installed .NET Framework version via registry
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.0.3705 (for 1.0), HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322 (for 1.1), or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727 (for 2.0). Check for the 'Install' value and 'Version' value under each key.
    Affected if Any of these registry keys show .NET Framework version 1.0 (any installed version), 1.1 (any installed version), or 2.0 (any installed version) is present.
  2. Verify .NET Framework presence via command line
    Open Command Prompt and run: dir %WINDIR%\Microsoft.NET\Framework\v1.0.3705 or dir %WINDIR%\Microsoft.NET\Framework\v1.1.4322 or dir %WINDIR%\Microsoft.NET\Framework\v2.0.50727 to check if the respective version directories exist.
    Affected if Any of these version directories exist in the Windows Microsoft.NET Framework folder.
  3. Confirm JIT Compiler component is present
    Check for the presence of mscorjit.dll in the .NET Framework directory. For v1.0 look in %WINDIR%\Microsoft.NET\Framework\v1.0.3705\mscorjit.dll, for v1.1 in %WINDIR%\Microsoft.NET\Framework\v1.1.4322\mscorjit.dll, and for v2.0 in %WINDIR%\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll.
    Affected if The mscorjit.dll file exists for any of the affected version directories, indicating the JIT Compiler component is installed.
  4. Check if .NET applications are running or configured
    Review installed programs list or check for .NET-dependent applications. Also verify if IIS is configured with ASP.NET enabled, as ASP.NET leverages the JIT compiler when serving managed code.
    Affected if ASP.NET is enabled in IIS or .NET applications are installed, as these would invoke the vulnerable JIT Compiler component.

Your environment is affected if .NET Framework version 1.0, 1.1, or 2.0 is installed and the JIT Compiler component (mscorjit.dll) is present on a Windows 2000, XP, Server 2003, or Vista system.

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 patches for the .NET JIT Compiler vulnerability (MS07-029) to affected .NET Framework versions on all supported Windows systems.

Recommended fix High confidence

Migrate from .NET Framework 1.0/1.1/2.0 to .NET Framework 4.8 (or .NET 6/7/8 for new development)

  1. 1. Identify all systems running .NET Framework 1.0, 1.1, or 2.0 in the environment
  2. 2. Since .NET Framework 1.0, 1.1, and 2.0 are all end-of-life and no longer receive security updates, plan migration to a supported .NET version
  3. 3. For .NET Framework 2.0 applications: Migrate to .NET Framework 3.5 (which includes 2.0 runtime) or preferably .NET Framework 4.8 (the last supported .NET Framework version)
  4. 4. For .NET Framework 1.1 applications: These will require code changes to target .NET Framework 3.5 or higher
  5. 5. For .NET Framework 1.0 applications: These will require significant code changes to target a supported .NET version
  6. 6. Test application functionality thoroughly after migration
  7. 7. Apply enterprise deployment best practices including rollback plans
  8. 8. If immediate upgrade is not feasible, implement network-based mitigations: restrict network access to affected systems, enable Enhanced Mitigation Experience Toolkit (EMET) if available, and prioritize systems by exposure to untrusted input
Caveat Migration from .NET Framework 1.x/2.0 to 4.x may require code changes due to API differences and deprecated features; thorough testing is essential

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0043 — 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-0043 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