CVE-2010-2561 Microsoft XML Core Services (aka MSXML) 3.0 does not properly handle HTTP responses, which allows remote attackers to execute arbitrary code
Critical 9.3
Published
Updated
Check this codebase for CVE-2010-2561 and fix it if it is affected.
What it is: CVE-2010-2561 is a critical vulnerability in n/a, published on 11 Aug 2010.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-2561 exists.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2010-2561/ (Markdown: https://insights.sbomify.com/CVE-2010-2561/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2010-2561?
CVE-2010-2561 is a critical vulnerability in n/a, published on 11 Aug 2010.
Official description
Microsoft XML Core Services (aka MSXML) 3.0 does not properly handle HTTP responses, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted response, aka "Msxml2.XMLHTTP.3.0 Response Handling Memory Corruption Vulnerability."
Weakness: CWE-94
Which versions are affected by CVE-2010-2561?
It affects 1 product.
Products include Microsoft Xml Core Services.
How do I fix CVE-2010-2561?
No fix has been published for CVE-2010-2561 yet. Limit exposure of the affected software until one is available.
Is CVE-2010-2561 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-2561 exists.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in n/a
- CVE-2012-1889 Microsoft XML Core Services Memory Corruption
- CVE-2007-2223 Integer overflow in n/a
- CVE-2016-0147 Microsoft XML Core Services 3.0 allows remote attackers to execute arbitrary code via a crafted web site, aka "MSXML 3.0 Remote Code Executi
- CVE-2006-5745 Memory corruption in n/a
- CVE-2006-4686 Memory corruption in n/a
Sources
Also known as GHSA-chj8-f33h-qgp9.