CVE-2018-16075 Information disclosure in Chrome
Medium 5.3
Published
Updated
Check this codebase for CVE-2018-16075 and fix it if it is affected.
What it is: CVE-2018-16075 is a medium-severity vulnerability in Google Chrome, published on 27 Jun 2019. 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-2018-16075 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-2018-16075/ (Markdown: https://insights.sbomify.com/CVE-2018-16075/index.md)
Remote attackers can read local files via crafted HTML pages due to insufficient file type enforcement in Chrome's Blink engine.
- 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-2018-16075?
CVE-2018-16075 is a medium-severity vulnerability in Google Chrome, published on 27 Jun 2019. 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
Insufficient file type enforcement in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to obtain local file data via a crafted HTML page.
Which versions are affected by CVE-2018-16075?
It affects 1 product.
Products include Google Chrome.
How do I fix CVE-2018-16075?
Upgrade to a fixed version.
Is CVE-2018-16075 being exploited?
There is no known exploitation of CVE-2018-16075 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-hmf6-x68j-3f6v, UBUNTU-CVE-2018-16075.