CVE-2016-9652 Multiple unspecified vulnerabilities in Google Chrome before 55.0.2883.75.
Critical 9.8
Published
Updated
Check this codebase for CVE-2016-9652 and fix it if it is affected.
What it is: CVE-2016-9652 is a critical vulnerability in Google Chrome, published on 20 Nov 2019.
Exploitation: There is no known exploitation of CVE-2016-9652 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-2016-9652/ (Markdown: https://insights.sbomify.com/CVE-2016-9652/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2016-9652?
CVE-2016-9652 is a critical vulnerability in Google Chrome, published on 20 Nov 2019.
Official description
Multiple unspecified vulnerabilities in Google Chrome before 55.0.2883.75.
Which versions are affected by CVE-2016-9652?
It affects 1 product.
Products include Google Chrome.
How do I fix CVE-2016-9652?
Upgrade to a fixed version.
Is CVE-2016-9652 being exploited?
There is no known exploitation of CVE-2016-9652 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-ch5q-r8mv-4p34, UBUNTU-CVE-2016-9652.