dbcve.org
Adobe Air Sdk And CompilerApplication · Adobe

CVE-2015-0301

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

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
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 do not properly validate files, which has unspecified impact and attack vectors.

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

Adobe Flash Player, AIR, and AIR SDK fail to properly validate files, allowing unspecified remote attack vectors. This is a critical file validation bypass that could enable arbitrary code execution via maliciously crafted SWF or other media files processed by the player.

MitigationUpdate to the patched versions: Flash Player 13.0.0.260/16.0.0.257 or later, AIR 16.0.0.245/272 or later, or AIR SDK 16.0.0.272 or later. If patching is not feasible, disable or restrict Flash Player usage.

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 Sdk And CompilerApplication
Affected:<= 15.0.0.356
Adobe AirApplication
Affected:<= 15.0.0.356
Adobe Air SdkApplication
Affected:<= 15.0.0.356
Flash PlayerApplication
Affected:= 11.2.202.425<= 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

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 Flash Player version in Windows browsers
    Open Internet Explorer and navigate to 'About Adobe Flash Player' (right-click on any Flash content and select 'About Adobe Flash Player'), or check the version in the Windows registry under HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion
    Affected if The displayed version is 11.2.202.425, or falls between 13.0.0.0 and 13.0.0.259 inclusive, or matches 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, or 15.0.0.238
  2. Identify installed Flash Player version in Linux
    Run 'rpm -q flash-player' or 'dpkg -l | grep flash' depending on the package manager, or check /usr/lib/flash-plugin/libflashplayer.so and use 'strings' to extract version info
    Affected if The version matches any of the affected versions listed above (11.2.202.425, 13.x.x.x up to 13.0.0.259, 14.0.0.125/145/176/179, or 15.0.0.144/152/167/189/223/238)
  3. Identify installed Adobe AIR version on Windows
    Open Windows Control Panel and look for 'Adobe AIR' in the Programs and Features list, or check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR
    Affected if The installed version is 15.0.0.356 or any earlier version (versions <= 15.0.0.356 are affected)
  4. Identify installed Adobe AIR SDK version
    Check the AIR SDK version by looking at the AIR SDK installer file used, or locate the 'version.xml' file within the AIR SDK installation directory (commonly in the 'AIR_SDK' or 'SDK' folder)
    Affected if The AIR SDK version is 15.0.0.356 or earlier (for Air Sdk And Compiler, Air, or Air Sdk components)
  5. Confirm Flash Player plugin is enabled and processing files
    Verify that the Flash Player browser plugin is enabled in the browser's add-on or plugin manager, and confirm the user can load SWF files or view content on websites using Flash
    Affected if The Flash plugin is active and the user processes SWF or other media files - the vulnerability is triggered when the player validates these files

A system is affected if it has Adobe Flash Player version 11.2.202.425, any version from 13.0.0.0 through 13.0.0.259, any of the specific 14.x or 15.x versions listed, or Adobe AIR / AIR SDK version 15.0.0.356 or earlier, AND the player processes SWF or media files.

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

Update to the patched versions: Flash Player 13.0.0.260/16.0.0.257 or later, AIR 16.0.0.245/272 or later, or AIR SDK 16.0.0.272 or later. If patching is not feasible, disable or restrict Flash Player usage.

Recommended fix High confidence

Adobe Flash Player 16.0.0.257+ (or 13.0.0.260+ for 13.x branch, 11.2.202.429+ for Linux); Adobe AIR 16.0.0.245+ (Windows/OS X) or 16.0.0.272+ (Android); Adobe AIR SDK 16.0.0.272+

  1. Identify the exact Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version currently installed
  2. For Adobe Flash Player on Windows/OS X: upgrade to version 16.0.0.257 or later (or 13.0.0.260 or later for the 13.x branch)
  3. For Adobe 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 or Adobe AIR SDK & Compiler: upgrade to version 16.0.0.272 or later
  7. Verify the installed version matches or exceeds the fixed release after upgrade
Caveat Upgrading Flash Player or AIR may affect existing SWF/ActionScript content compatibility; ensure testing in staging environment before production deployment

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

Fix this in Adobe Air Sdk And Compiler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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