CVE-2010-3111 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2010-3111 and fix it if it is affected.
What it is: CVE-2010-3111 is a critical vulnerability in Google Chrome, published on 24 Aug 2010.
Exploitation: There is no known exploitation of CVE-2010-3111 in the wild and no public exploit code.
Affected product: Google Chrome. 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-3111/ (Markdown: https://insights.sbomify.com/CVE-2010-3111/index.md)
Google Chrome fails to properly mitigate an unspecified Windows kernel flaw, potentially allowing attackers to exploit the underlying system vulnerability.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2010-3111?
CVE-2010-3111 is a critical vulnerability in Google Chrome, published on 24 Aug 2010.
Official description
Google Chrome before 6.0.472.53 does not properly mitigate an unspecified flaw in the Windows kernel, which has unknown impact and attack vectors, a different vulnerability than CVE-2010-2897.
Which versions are affected by CVE-2010-3111?
It affects 1 product.
Products include Google Chrome.
How do I fix CVE-2010-3111?
No fix has been published for CVE-2010-3111 yet. Limit exposure of the affected software until one is available.
Is CVE-2010-3111 being exploited?
There is no known exploitation of CVE-2010-3111 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-cxv3-xv97-w4pp.