# CVE-2011-3420: Other in n/a

> Unspecified vulnerabilities in Google Chrome on specific Chromebook platforms allow attackers to potentially compromise the system.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 10 Sep 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cp6p-2hpf-w8gp, UBUNTU-CVE-2011-3420

## What is CVE-2011-3420?

CVE-2011-3420 is a critical vulnerability in Google Chrome Os, published on 10 Sep 2011. 

### Official description

Multiple unspecified vulnerabilities in Google Chrome before 14.0.835.157 on the Acer AC700, Samsung Series 5, and Cr-48 Chromebook platforms have unknown impact and attack vectors.

## Which versions are affected by CVE-2011-3420?

It affects 4 products.


Products: Acer Ac700 Chromebook, Google Chrome Os, Google Cr-48 Chromebook, Samsung Series 5 Chromebook.

## How do I fix CVE-2011-3420?

No fix has been published for CVE-2011-3420 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-3420 being exploited?

There is no known exploitation of CVE-2011-3420 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome Os

- [CVE-2012-3290](https://insights.sbomify.com/CVE-2012-3290/): Other in n/a (critical 10.0)
- [CVE-2012-1418](https://insights.sbomify.com/CVE-2012-1418/): Other in n/a (critical 10.0)
- [CVE-2012-0695](https://insights.sbomify.com/CVE-2012-0695/): Other in n/a (critical 10.0)
- [CVE-2011-4719](https://insights.sbomify.com/CVE-2011-4719/): Other in n/a (critical 10.0)
- [CVE-2011-4548](https://insights.sbomify.com/CVE-2011-4548/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3420 and fix it if it is affected.

What it is: CVE-2011-3420 is a critical vulnerability in Google Chrome Os, published on 10 Sep 2011. 
Exploitation: There is no known exploitation of CVE-2011-3420 in the wild and no public exploit code.

Affected product: Google Chrome Os. 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-2011-3420/ (Markdown: https://insights.sbomify.com/CVE-2011-3420/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-3420
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-3420
- OSV: https://osv.dev/vulnerability/CVE-2011-3420

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-3420/
Summaries are generated and may contain mistakes; the official description above is the record.