dbcve.org
ChromeWeb browser · Google

CVE-2015-1247

MEDIUM · 5.0 CVSS v2.0 Published 2015-04-19
Fix available
A fix is available. Upgrade to after 42.0.2311.60 or later.
See remediation →
59/100
Remediation priority · Elevated
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
The SearchEngineTabHelper::OnPageHasOSDD function in browser/ui/search_engines/search_engine_tab_helper.cc in Google Chrome before 42.0.2311.90 does not prevent use of a file: URL for an OpenSearch descriptor XML document, which might allow remote attackers to obtain sensitive information from local files via a crafted (1) http or (2) https web site.

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

In Google Chrome before 42.0.2311.90, the SearchEngineTabHelper::OnPageHasOSDD function fails to validate the URL scheme of OpenSearch descriptor XML documents, allowing file: URLs to be processed. This enables a malicious http/https website to trigger the browser into reading local files from the filesystem via the file: protocol, leading to information disclosure.

MitigationUpgrade Google Chrome to version 42.0.2311.90 or later, which includes proper validation to reject file: URLs in OpenSearch descriptor processing.

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:<= 42.0.2311.60
Debian LinuxOperating system
Affected:= 7.0

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
Partial
Integrity
None
Availability
None

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

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. Check installed Google Chrome version
    Open chrome://version in the browser address bar, or run 'google-chrome --version' or 'chrome --version' from command line
    Affected if Version is 42.0.2311.60 or lower, or any version below 42.0.2311.90
  2. Verify Chrome version on Debian Linux
    If on Debian, run 'dpkg -l | grep google-chrome' or check the installed package version with apt policy google-chrome-stable
    Affected if The installed package version is 42.0.2311.90-1 or lower
  3. Confirm Chrome is the default or active browser
    Check if Chrome is set as the default browser or commonly used browser on the system
    Affected if Chrome is actively used for web browsing, making it a potential vector for malicious websites to exploit this flaw

You are affected if Google Chrome version is 42.0.2311.60 or lower (below the fixed 42.0.2311.90), regardless of operating system, or if you are on Debian 7.0 with an unpatched Chrome package.

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.

From vendor data
Upgrade available Upgrade to a release after 42.0.2311.60
Interim mitigation

Upgrade Google Chrome to version 42.0.2311.90 or later, which includes proper validation to reject file: URLs in OpenSearch descriptor processing.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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