CVE-2016-5176 Security feature bypass in n/a
Medium 6.5
Published
Updated
Check this codebase for CVE-2016-5176 and fix it if it is affected.
What it is: CVE-2016-5176 is a medium-severity vulnerability in Google Chrome, published on 29 Sep 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-5176 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-5176/ (Markdown: https://insights.sbomify.com/CVE-2016-5176/index.md)
Remote attackers can bypass Chrome's SafeBrowsing protection mechanism, potentially exposing users to malicious content.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2016-5176?
CVE-2016-5176 is a medium-severity vulnerability in Google Chrome, published on 29 Sep 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Google Chrome before 53.0.2785.113 allows remote attackers to bypass the SafeBrowsing protection mechanism via unspecified vectors.
Weakness: CWE-284
Which versions are affected by CVE-2016-5176?
It affects 1 product.
Products include Google Chrome.
How do I fix CVE-2016-5176?
Upgrade to a fixed version.
Is CVE-2016-5176 being exploited?
There is no known exploitation of CVE-2016-5176 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-j9pw-r36r-r9cp, UBUNTU-CVE-2016-5176.