dbcve.org
Adobe Air SdkApplication · Adobe

CVE-2015-0304

HIGH · 10.0 CVSS v2.0 Published 2015-01-13
Fix available
A fix is available. Upgrade to after 15.0.0.356 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Heap-based buffer overflow in Adobe Flash Player before 13.0.0.260 and 14.x through 16.x before 16.0.0.257 on Windows and OS X and before 11.2.202.429 on Linux, Adobe AIR before 16.0.0.245 on Windows and OS X and before 16.0.0.272 on Android, Adobe AIR SDK before 16.0.0.272, and Adobe AIR SDK & Compiler before 16.0.0.272 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-0309.

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

Heap-based buffer overflow vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution via unspecified vectors. The flaw affects multiple versions across Windows, OS X, Linux, and Android platforms. This is distinct from the related CVE-2015-0309.

MitigationUpdate Adobe Flash Player to version 13.0.0.260, 14.x/15.x to 16.0.0.257, or 16.x to 16.0.0.257 (or later). Update Adobe AIR to 16.0.0.245 (Windows/OS X), 16.0.0.272 (Android), and Adobe AIR SDK to 16.0.0.272 or later.

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
Adobe Air SdkApplication
Affected:<= 15.0.0.356
Adobe AirApplication
Affected:<= 15.0.0.356
Adobe Air Sdk And CompilerApplication
Affected:<= 15.0.0.356
Flash PlayerApplication
Affected:<= 13.0.0.259= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.144= 15.0.0.152= 15.0.0.167= 15.0.0.189= 15.0.0.223= 15.0.0.238= 15.0.0.239

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
Complete
Integrity
Complete
Availability
Complete

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

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 installed Adobe Flash Player version
    On Windows, check the file properties of the Flash Player plugin (NPSWF32.dll or Flash32_*.ocx) in the browser plugins directory, or query the registry key HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion. On macOS, check /Library/Internet Plug-Ins/Flash Player.plugin/Contents/info.plist or the file version of Flash Player.plugin. On Linux, check /usr/lib/flash-plugin/libflashplayer.so or the version file in that directory.
    Affected if The installed version is 13.0.0.259 or earlier, or matches any of these: 14.0.0.125, 14.0.0.145, 14.0.0.176, 14.0.0.179, 15.0.0.144, 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.238, or 15.0.0.239
  2. Identify installed Adobe AIR version
    On Windows, check Add/Remove Programs for Adobe AIR, or check the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR for DisplayVersion. On macOS, check /Applications/Adobe AIR Installer.app or the Info.plist within it for CFBundleVersion. On Android, check Settings > Apps > Adobe AIR for the version.
    Affected if The installed version is 15.0.0.356 or any earlier version (15.0.0.x range up to 356)
  3. Check for Adobe AIR SDK installation
    If you develop AIR applications, locate the AIR SDK directory. Check the version file (often version.txt or flex-sdk-description.xml) within the SDK folder, or right-click the AIR SDK folder and view Properties > Details to find the version.
    Affected if The AIR SDK version is 15.0.0.356 or earlier

You are affected if any installed Flash Player version matches the affected list (13.0.0.259 and earlier, or any of the specific 14.x/15.x versions listed) or if Adobe AIR/SDK version is 15.0.0.356 or earlier.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 15.0.0.356
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.260, 14.x/15.x to 16.0.0.257, or 16.x to 16.0.0.257 (or later). Update Adobe AIR to 16.0.0.245 (Windows/OS X), 16.0.0.272 (Android), and Adobe AIR SDK to 16.0.0.272 or later.

Recommended fix High confidence

Adobe Flash Player 16.0.0.257 (or 13.0.0.260 for legacy 13.x); Adobe AIR 16.0.0.245 (Windows/OS X) / 16.0.0.272 (Android); Adobe AIR SDK 16.0.0.272

  1. Identify the specific Adobe product installed (Flash Player, Adobe AIR, or Adobe AIR SDK) and its current version
  2. For Flash Player on Windows/OS X: upgrade to version 13.0.0.260 or 16.0.0.257 or later
  3. For Flash Player on Linux: upgrade to version 11.2.202.429 or later
  4. For Adobe AIR on Windows/OS X: upgrade to version 16.0.0.245 or later
  5. For Adobe AIR on Android: upgrade to version 16.0.0.272 or later
  6. For Adobe AIR SDK: upgrade to version 16.0.0.272 or later
  7. Verify the installed version matches or exceeds the fixed release after upgrade
  8. Confirm the vulnerability is remediated
Caveat This is a security-only update with minimal compatibility impact; however, some legacy Flash content may require testing after upgrading

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

Fix this in Adobe Air Sdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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