ChromeWeb browser · Google

CVE-2014-3159

MEDIUM · 6.4 CVSS v2.0 Published 2014-07-20

Fix available

A fix is available. Upgrade to after 36.0.1985.106 or later.

See remediation →

73/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The WebContentsDelegateAndroid::OpenURLFromTab function in components/web_contents_delegate_android/web_contents_delegate_android.cc in Google Chrome before 36.0.1985.122 on Android does not properly restrict URL loading, which allows remote attackers to spoof the URL in the Omnibox via unspecified vectors.

Technical summary

dbcve analysis · moderate confidence

This is a URL spoofing vulnerability in Google Chrome for Android versions before 36.0.1985.122. The WebContentsDelegateAndroid::OpenURLFromTab function in the web contents delegate component fails to properly restrict URL loading, allowing remote attackers to manipulate the URL displayed in the Omnibox to show a different address than the one actually being accessed.

MitigationUpdate Google Chrome for Android to version 36.0.1985.122 or later. For organizations, deploy the patched browser version through mobile device management (MDM) or enterprise mobility policies.

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

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:<= 36.0.1985.106= 36.0.1985.1= 36.0.1985.2= 36.0.1985.3= 36.0.1985.4= 36.0.1985.5= 36.0.1985.6= 36.0.1985.8= 36.0.1985.12= 36.0.1985.13= 36.0.1985.14= 36.0.1985.15

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: None

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

Am I affected?

dbcve checks

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

Verify the device platform is Android

Check the device operating system. This vulnerability affects only Google Chrome running on Android devices. On the Android device, go to Settings > About Phone/Tablet to confirm Android OS is running.

Affected if The device is not running Android OS - this CVE does not apply to iOS, Windows, Mac, or Linux versions of Chrome.
Confirm Google Chrome for Android is installed

On the Android device, open the app drawer or Play Store and verify Google Chrome browser is installed. Alternatively, check Settings > Apps for Chrome.

Affected if Google Chrome is not installed - the device may be using a different browser (e.g., Samsung Internet, Firefox) which is not affected by this specific CVE.
Determine the installed Google Chrome version

Open Google Chrome > tap the three-dot menu > tap Help > tap About Chrome. The version number will be displayed (for example, 36.0.1985.106).

Affected if Unable to determine the version - the detection check cannot be completed.
Compare installed version against affected ranges

Review the version identified in step 3. The affected versions are: any version less than or equal to 36.0.1985.106; OR exactly matching one of these: 36.0.1985.1, 36.0.1985.2, 36.0.1985.3, 36.0.1985.4, 36.0.1985.5, 36.0.1985.6, 36.0.1985.8, 36.0.1985.12, 36.0.1985.13, 36.0.1985.14, 36.0.1985.15.

Affected if The installed version is 36.0.1985.106 or lower, or exactly matches one of the specific affected versions listed. Versions 36.0.1985.122 and later are not affected.

The environment is affected if Google Chrome for Android is installed and the version number is 36.0.1985.106 or lower, or matches any of the specific affected versions (36.0.1985.1 through 36.0.1985.15).

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 36.0.1985.106

Interim mitigation

Update Google Chrome for Android to version 36.0.1985.122 or later. For organizations, deploy the patched browser version through mobile device management (MDM) or enterprise mobility policies.

Fix this in Chrome Scoped from the published advisory

Consultation1.0 h
Implementation2.0 h
Testing1.0 h
Review / QA1.0 h

5.0 hours of engineering $890

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,424.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2014-3159?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 36.0.1985.106 or later

Severity 6.4 Medium

Exploit likelihood EPSS, next 30 days 0.9%

Affects: Chrome

Remediation

Need this fixed?

Fix this in Chrome 5 hrs · Low

Typical engagement from $890

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2014-3159 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References