dbcve.org
Chrome OsOperating system · Google

CVE-2012-3290

HIGH · 10.0 CVSS v2.0 Published 2012-06-07
Fix available
A fix is available. Upgrade to after 20.0.1132.21 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple unspecified vulnerabilities in Google Chrome before 20.0.1132.22 on the Acer AC700; Samsung Series 5, 5 550, and Chromebox 3; and Cr-48 Chromebook platforms have unknown impact and attack vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Multiple unspecified vulnerabilities in Google Chrome before version 20.0.1132.22 on specific Chromebook and Chromebox platforms (Acer AC700, Samsung Series 5/550, Chromebox 3, Cr-48) with unknown impact and attack vectors. The vulnerabilities are tied to a particular Chrome version and hardware platform combination from 2012.

MitigationUpgrade Google Chrome to version 20.0.1132.22 or later on affected Acer AC700, Samsung Series 5/550, Chromebox 3, and Cr-48 Chromebooks. If the platform cannot support newer Chrome versions, consider retiring or isolating the affected hardware.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Chrome OsOperating system
Affected:<= 20.0.1132.21= 20.0.1132.0= 20.0.1132.1= 20.0.1132.2= 20.0.1132.3= 20.0.1132.4= 20.0.1132.5= 20.0.1132.6= 20.0.1132.7= 20.0.1132.8= 20.0.1132.9= 20.0.1132.10
Cr 48 ChromebookHardware / appliance
Affected:all versions
Ac700 ChromebookHardware / appliance
Affected:all versions
Chromebox 3Hardware / appliance
Affected:all versions
Series 5 550 ChromebookHardware / appliance
Affected:all versions
Series 5 ChromebookHardware / appliance
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the device model or product name (typically found in system settings, on the device label, or via `chrome://system` in the browser)
    Affected if The device is NOT one of: Acer AC700, Samsung Series 5, Samsung Series 5 550, Samsung Chromebox 3, or Cr-48 - if so, this CVE does not apply
  2. Determine Chrome OS version
    Open chrome://settings or use the command `chrome://system` to view the Chrome OS version number
    Affected if The installed Chrome OS version is greater than 20.0.1132.21 (the fix is in 20.0.1132.22 or later) - if so, this CVE does not apply
  3. Confirm affected version range
    Compare your installed version against the affected list: versions <= 20.0.1132.21 OR exact versions 20.0.1132.0 through 20.0.1132.10
    Affected if Your version exactly matches one of the affected versions listed in the CVE

You are affected only if you are using one of the specified hardware platforms (Acer AC700, Samsung Series 5/550, Samsung Chromebox 3, or Cr-48) AND your Chrome OS version is either <= 20.0.1132.21 or matches any of the specific point versions 20.0.1132.0 through 20.0.1132.10.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 20.0.1132.21
Interim mitigation

Upgrade Google Chrome to version 20.0.1132.22 or later on affected Acer AC700, Samsung Series 5/550, Chromebox 3, and Cr-48 Chromebooks. If the platform cannot support newer Chrome versions, consider retiring or isolating the affected hardware.

Recommended fix High confidence

Chrome OS version 20.0.1132.22

  1. 1. Check the current Chrome OS version on the device by navigating to chrome://settings/help
  2. 2. If the version is 20.0.1132.21 or earlier, attempt to check for system updates through Settings > About Chrome OS > Check for updates
  3. 3. Apply the system update to upgrade to version 20.0.1132.22 which contains the security fixes
Caveat These are legacy devices from 2012; some may no longer receive automatic updates from Google and may have very limited update channels available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Os Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-3290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-3290 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data