CVE-2014-1681 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2014-1681 and fix it if it is affected.
What it is: CVE-2014-1681 is a critical vulnerability in Google Chrome, published on 28 Jan 2014. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2014-1681 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-2014-1681/ (Markdown: https://insights.sbomify.com/CVE-2014-1681/index.md)
Multiple unspecified security flaws in Google Chrome allow attackers to potentially compromise the browser, requiring an upgrade to the latest version.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not stated
- Fix
- Available
What is CVE-2014-1681?
CVE-2014-1681 is a critical vulnerability in Google Chrome, published on 28 Jan 2014. It can be exploited over the network.
Official description
Multiple unspecified vulnerabilities in Google Chrome before 32.0.1700.102 have unknown impact and attack vectors, related to 12 "security fixes [that were not] either contributed by external researchers or particularly interesting."
Which versions are affected by CVE-2014-1681?
It affects 1 product.
Products include Google Chrome.
How do I fix CVE-2014-1681?
Upgrade to a fixed version.
Is CVE-2014-1681 being exploited?
There is no known exploitation of CVE-2014-1681 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-6fwp-q266-h3x2.