dbcve.org
Debian LinuxOperating system · Debian

CVE-2015-1260

HIGH · 7.5 CVSS v2.0 Published 2015-05-20
Fix available
A fix is available. Upgrade to after 42.0.2311.152 or later.
See remediation →
84/100
Remediation priority · High
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 use-after-free vulnerabilities in content/renderer/media/user_media_client_impl.cc in the WebRTC implementation in Google Chrome before 43.0.2357.65 allow remote attackers to cause a denial of service or possibly have unspecified other impact via crafted JavaScript code that executes upon completion of a getUserMedia request.

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

Use-after-free vulnerabilities in WebRTC's user_media_client_impl.cc allow remote attackers to trigger the vulnerability via malicious JavaScript that executes upon completion of a getUserMedia request (camera/microphone access), potentially leading to denial of service or arbitrary code execution.

MitigationUpdate Google Chrome to version 43.0.2357.65 or later to patch the use-after-free vulnerabilities in the WebRTC implementation.

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
Debian LinuxOperating system
Affected:= 8.0
ChromeWeb browser
Affected:<= 42.0.2311.152

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

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

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 installed browser
    Open chrome://version or check the browser executable to confirm whether the browser is Google Chrome
    Affected if The browser is Google Chrome and the version is 42.0.2311.152 or lower
  2. Check the Google Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' from command line
    Affected if The reported version is 42.0.2311.152 or any version lower than 42.x
  3. Confirm WebRTC module status
    Navigate to chrome://flags/#enable-webrtc or check if WebRTC is listed in chrome://components
    Affected if WebRTC is enabled (the vulnerability requires getUserMedia functionality to be available)
  4. Verify camera/microphone permissions
    Check chrome://settings/content for camera and microphone permissions, or inspect active content settings
    Affected if Camera or microphone access has been granted to any website (the exploit triggers upon getUserMedia request completion)

You are affected if you are running Google Chrome version 42.0.2311.152 or lower with WebRTC enabled and have granted camera or microphone permissions to websites.

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.152
Interim mitigation

Update Google Chrome to version 43.0.2357.65 or later to patch the use-after-free vulnerabilities in the WebRTC implementation.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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