CVE-2007-0043 in the critical feed json
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 u…
published 19y ago modified 5mo ago also EUVD-2007-0047
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 30.7%
- EPSS 30.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
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".
Is CVE-2007-0043 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
30.67% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
-
archive.cert.uni-stuttgart.de
/bugtraq/2007/07/msg00254.html
vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2007/ms07-040
vendor-advisory
-
vupen.com
/english/advisories/2007/2482
vdb-entry, vendor-advisory
-
secunia.com
/advisories/26003
third-party-advisory, vendor-advisory
-
osvdb.org
/35956
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1873
vdb-entry, signature
-
exchange.xforce.ibmcloud.com
/vulnerabilities/34639
vdb-entry
-
us-cert.gov
/cas/techalerts/TA07-191A.html
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1018356
vdb-entry
-
securityfocus.com
/bid/24811
vdb-entry
Sources
- CVE List CVE-2007-0043
- NVD CVE-2007-0043
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.