dbcve.org
ChromeWeb browser · Google

CVE-2012-4907

HIGH · 9.3 CVSS v2.0 Published 2012-09-13
Fix available
A fix is available. Upgrade to after 18.0.1025306 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
Google Chrome before 18.0.1025308 on Android does not properly restrict access from JavaScript code to Android APIs, which allows remote attackers to have an unspecified impact via a crafted web page.

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 · moderate confidence

Google Chrome before 18.0.1025308 on Android contains a vulnerability in the JavaScript-to-native API bridge mechanism that fails to properly restrict JavaScript access to sensitive Android system APIs. Remote attackers can exploit this by tricking users into visiting crafted web pages that execute malicious JavaScript to interact with device capabilities without user consent.

MitigationUpdate Google Chrome for Android to version 18.0.1025308 or later. For enterprise environments, utilize mobile device management (MDM) tools to identify and push Chrome updates to all managed Android devices.

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
ChromeWeb browser
Affected:<= 18.0.1025306

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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. Verify Google Chrome for Android is installed
    Open the Android device settings, go to Apps or Application Manager, and look for Google Chrome in the list of installed applications
    Affected if Google Chrome is present on the device and its version is 18.0.1025306 or lower
  2. Determine the installed Chrome version
    Open Google Chrome, tap the three-dot menu, go to Settings, scroll to About Chrome or Chrome version to display the full version number (e.g., 18.0.1025XXX)
    Affected if The displayed version number is 18.0.1025306 or lower, indicating a vulnerable version
  3. Confirm the vulnerable version range
    Compare the installed version number against the affected range: any version <= 18.0.1025306 is vulnerable
    Affected if The version shown is 18.0.1025306, 18.0.1025305, 18.0.1025300, or any earlier 18.0.x release
  4. Identify if the browser has JavaScript capability enabled
    Chrome for Android has JavaScript enabled by default; this is controlled via Settings > Site settings > JavaScript (should be set to Allowed for normal browsing)
    Affected if JavaScript is enabled in Chrome settings, which is required for the exploitation vector through malicious web pages

The device is affected if Google Chrome for Android version 18.0.1025306 or lower is installed and JavaScript browsing is enabled, allowing remote attackers to exploit the JavaScript-to-native API bridge via malicious webpages.

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 18.0.1025306
Interim mitigation

Update Google Chrome for Android to version 18.0.1025308 or later. For enterprise environments, utilize mobile device management (MDM) tools to identify and push Chrome updates to all managed Android devices.

Recommended fix High confidence

Chrome Android 18.0.1025308 or later

  1. Open the Google Play Store app on your Android device
  2. Search for "Google Chrome" or "Chrome"
  3. Tap on Google Chrome from the search results
  4. If an update is available, tap the "Update" button
  5. Wait for the update to download and install
  6. Alternatively, enable automatic updates by going to Play Store > Settings > Auto-update apps > Auto-update apps over any network or Wi-Fi only
  7. After updating, verify the version by opening Chrome, tapping the three-dot menu, going to Settings > About Chrome to confirm version 18.0.1025308 or later is installed

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-4907 — 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-4907 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