dbcve.org
ChromeWeb browser · Google

CVE-2013-2846

HIGH · 7.5 CVSS v2.0 Published 2013-05-22
Fix available
A fix is available. Upgrade to after 27.0.1453.91 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
Use-after-free vulnerability in the media loader in Google Chrome before 27.0.1453.93 allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors, a different vulnerability than CVE-2013-2840.

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 vulnerability in Google Chrome's media loader component (before version 27.0.1453.93) allows remote attackers to cause denial of service or potentially achieve unspecified code execution via unknown vectors. The flaw involves improper memory management when handling media content, leading to freed memory being accessed after deallocation.

MitigationUpdate Google Chrome to version 27.0.1453.93 or later. In enterprise environments, ensure automated patch deployment or manually push the browser update to all affected workstations.

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:<= 27.0.1453.91= 27.0.1453.0= 27.0.1453.1= 27.0.1453.2= 27.0.1453.3= 27.0.1453.4= 27.0.1453.5= 27.0.1453.6= 27.0.1453.7= 27.0.1453.8= 27.0.1453.9= 27.0.1453.10

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. Check installed Chrome version
    Navigate to chrome://version in the Chrome browser address bar and note the version number displayed under 'Google Chrome'
    Affected if The version shown is 27.0.1453.0 through 27.0.1453.91, or any version <= 27.0.1453.91
  2. Verify via command line (optional)
    Open a command prompt or terminal and run: chrome --version (Windows) or /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version (macOS)
    Affected if The reported version falls within 27.0.1453.0 to 27.0.1453.91
  3. Confirm media loader is in use
    This vulnerability affects the media loader component. Check if Chrome is configured to handle media content (audio/video). This is enabled by default in Chrome; no special configuration needed to be vulnerable.
    Affected if Chrome handles any media content (video playback, audio playback, embedded media on web pages)

You are affected if your installed Google Chrome version is 27.0.1453.0 through 27.0.1453.91 (or any version <= 27.0.1453.91), as these versions contain the vulnerable media loader component.

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

Update Google Chrome to version 27.0.1453.93 or later. In enterprise environments, ensure automated patch deployment or manually push the browser update to all affected workstations.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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