Flash PlayerApplication · Adobe

CVE-2015-3134

HIGH · 10.0 CVSS v2.0 Published 2015-07-09

Fix available

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

See remediation →

100/100

Remediation priority · Urgent

Public exploit Remotely reachable No privileges Zero-click Patch available

Official description

NVD · unedited

Adobe Flash Player before 13.0.0.302 and 14.x through 18.x before 18.0.0.203 on Windows and OS X and before 11.2.202.481 on Linux, Adobe AIR before 18.0.0.180, Adobe AIR SDK before 18.0.0.180, and Adobe AIR SDK & Compiler before 18.0.0.180 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-3117, CVE-2015-3123, CVE-2015-3130, CVE-2015-3133, and CVE-2015-4431.

Technical summary

dbcve analysis · high confidence

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution. Affects specific versions across Windows, OS X, and Linux platforms. The vulnerability has critical severity (CVSS 10) indicating network-exploitable, unauthenticated attacks with complete system compromise potential.

MitigationApply vendor patches by updating Adobe Flash Player to version 13.0.0.302, 18.0.0.203, or 11.2.202.481 (Linux), and Adobe AIR to version 18.0.0.180 or later.

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

Flash PlayerApplication

Affected:<= 11.2.202.468<= 13.0.0.289= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.152= 15.0.0.167= 15.0.0.189= 15.0.0.223= 15.0.0.239= 15.0.0.246

AirApplication

Affected:<= 18.0.0.144

Air SdkApplication

Affected:<= 18.0.0.144

Air Sdk \& CompilerApplication

Affected:<= 18.0.0.144

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.

Identify installed Adobe Flash Player version

On Windows, check Add/Remove Programs for Adobe Flash Player or inspect the flash*.ocx file properties. On macOS, check /Library/Application Support/Adobe/Flash Player or the Applications folder. On Linux, run 'dpkg -l | grep flash' or 'rpm -qa | grep flash'

Affected if Version is 11.2.x <= 11.2.202.468, 13.0.x <= 13.0.0.289, any 14.0.0.x (125/145/176/179), or any 15.0.0.x (152/167/189/223/239/246)
Identify installed Adobe AIR version

On Windows, check Add/Remove Programs for Adobe AIR or inspect the AIR folder in Program Files. On macOS, check /Library/Application Support/Adobe/AIR or the Applications folder. Run 'reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR' on Windows

Affected if Version is <= 18.0.0.144
Identify installed Adobe AIR SDK version

Check the AIR SDK installation directory for version file or manifest. Common paths: Windows: C:\Program Files (x86)\Adobe\Adobe AIR SDK, macOS: /Applications/Adobe AIR SDK, Linux: /opt/adobe-air-sdk. Run 'air-sdk-version' command if available

Affected if AIR SDK version is <= 18.0.0.144
Identify installed Adobe AIR SDK and Compiler version

Check for the combined AIR SDK + Compiler package. Inspect version file in the SDK installation directory or run 'adt -version' if AIR SDK tools are on PATH

Affected if AIR SDK & Compiler version is <= 18.0.0.144

You are affected if any installed Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version matches or falls below the affected version ranges listed for this CVE.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 18.0.0.144

Vendor patch helpx.adobe.com →

Interim mitigation

Apply vendor patches by updating Adobe Flash Player to version 13.0.0.302, 18.0.0.203, or 11.2.202.481 (Linux), and Adobe AIR to version 18.0.0.180 or later.

Recommended fix High confidence

Flash Player 13.0.0.302+ (13.x) or 18.0.0.203+ (14.x-18.x) / AIR 18.0.0.180+

1. Determine the currently installed Adobe Flash Player version by visiting https://helpx.adobe.com/flash-player.html or checking Add/Remove Programs
2. For Flash Player: Upgrade to version 13.0.0.302 or later (13.x), or version 18.0.0.203 or later (14.x-18.x) for Windows/OS X, or version 11.2.202.481 or later for Linux
3. For Adobe AIR: Upgrade to version 18.0.0.180 or later
4. For Adobe AIR SDK: Upgrade to version 18.0.0.180 or later
5. For Adobe AIR SDK & Compiler: Upgrade to version 18.0.0.180 or later
6. Download from the official Adobe security bulletin at https://helpx.adobe.com/security/products/flash-player/apsb15-16.html
7. Verify the upgrade was successful by checking the installed version

Caveat Adobe Flash Player is deprecated and no longer supported as of end-of-life; consider migrating away from Flash-based content

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

Fix this in Flash Player 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-3134 — 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-3134 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-3134?

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

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 26.5%

Affects: Flash Player

Remediation

A high-priority fix

Fix this in Flash Player 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-3134 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