ChromeWeb browser · Google

CVE-2015-8480

HIGH · 10.0 CVSS v2.0 Published 2015-12-06

Fix available

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

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The VideoFramePool::PoolImpl::CreateFrame function in media/base/video_frame_pool.cc in Google Chrome before 47.0.2526.73 does not initialize memory for a video-frame data structure, which might allow remote attackers to cause a denial of service (out-of-bounds memory access) or possibly have unspecified other impact by leveraging improper interaction with the vp3_h_loop_filter_c function in libavcodec/vp3dsp.c in FFmpeg.

Technical summary

dbcve analysis · high confidence

Memory initialization vulnerability in Google Chrome's VideoFramePool::PoolImpl::CreateFrame function (media/base/video_frame_pool.cc) prior to version 47.0.2526.73. The function fails to properly initialize memory for video-frame data structures, leading to potential out-of-bounds memory access when interacting with FFmpeg's vp3_h_loop_filter_c function in libavcodec.

MitigationUpdate Google Chrome to version 47.0.2526.73 or later to receive the memory initialization fix. For enterprise environments, deploy the updated browser version through standard patch management processes.

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:<= 46.0.2490.86

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Confirm Google Chrome installation

Check if Google Chrome is installed by looking for chrome.exe in typical installation paths (e.g., C:\Program Files\Google\Chrome\Application\ or /Applications/Google Chrome.app on macOS) or run 'google-chrome --version' on Linux

Affected if Google Chrome is not installed on the system
Determine installed Google Chrome version

Open Google Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' from command line. The version number is displayed (e.g., 46.0.2490.86)

Affected if Unable to retrieve version information
Compare version against affected range

Compare your installed version number to the affected range: any version of Google Chrome less than or equal to 46.0.2490.86 (versions 46.x.x.x and below)

Affected if Installed version is 46.0.2490.86 or any earlier version (e.g., 45.x.x.x, 44.x.x.x)
Verify Chrome is used for video playback

This vulnerability exists in the VideoFramePool component used by Chrome's media subsystem. No additional feature toggle required - the affected code path is engaged during any video playback using Chrome's internal media handling

Affected if Chrome with affected version is used for web video content playback (the vulnerable code runs automatically during video frame allocation)

A user is affected if they are running Google Chrome version 46.0.2490.86 or any earlier version, as the vulnerable uninitialized memory code in the VideoFramePool executes during video playback.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 46.0.2490.86

Interim mitigation

Update Google Chrome to version 47.0.2526.73 or later to receive the memory initialization fix. For enterprise environments, deploy the updated browser version through standard patch management processes.

Recommended fix High confidence

Chrome 47.0.2526.73 or later

Open Chrome and navigate to Settings > Help > About Google Chrome
Verify your current version is below 47.0.2526.73
If an update is available, click 'Update Google Chrome'
Restart Chrome to complete the update

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

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-2015-8480 — 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-2015-8480 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-8480?

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 46.0.2490.86 or later

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 1.3%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 5 hrs · Low

Typical engagement from $890

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2015-8480 and return a fixed quote and timeline.

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