CVE-2010-2084 Microsoft ASP.NET 2.0 does not prevent setting the InnerHtml property on a control that inherits from HtmlContainerControl, which allows rem
Medium 4.3
Published
Updated
Check this codebase for CVE-2010-2084 and fix it if it is affected.
What it is: CVE-2010-2084 is a medium-severity vulnerability in n/a, published on 27 May 2010.
Exploitation: There is no known exploitation of CVE-2010-2084 in the wild and no public exploit code.
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-2084/ (Markdown: https://insights.sbomify.com/CVE-2010-2084/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2010-2084?
CVE-2010-2084 is a medium-severity vulnerability in n/a, published on 27 May 2010.
Official description
Microsoft ASP.NET 2.0 does not prevent setting the InnerHtml property on a control that inherits from HtmlContainerControl, which allows remote attackers to conduct cross-site scripting (XSS) attacks via vectors related to an attribute.
Weakness: CWE-79
Which versions are affected by CVE-2010-2084?
It affects 1 product.
Products include Microsoft Asp.net.
How do I fix CVE-2010-2084?
No fix has been published for CVE-2010-2084 yet. Limit exposure of the affected software until one is available.
Is CVE-2010-2084 being exploited?
There is no known exploitation of CVE-2010-2084 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-6r9p-jrjw-m3vj.