dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-0306

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
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 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-0303.

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

Memory corruption vulnerability in Adobe Flash Player and AIR allowing arbitrary code execution via unspecified vectors. Affects multiple versions across Windows, OS X, Linux, and Android platforms.

MitigationUpdate Adobe Flash Player to version 13.0.0.260+/16.0.0.257+ (Win/OSX), 11.2.202.429+ (Linux), and Adobe AIR to 16.0.0.245+ (Win/OSX) or 16.0.0.272+ (Android/SDK).

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

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 if Adobe Flash Player is installed
    Windows: Check registry key HKLM\SOFTWARE\Macromedia\FlashPlayer or look in C:\Windows\System32\Macromed\Flash. Mac: Check /Library/Internet\Plug-Ins/Flash Player.plugin or ~/Library/Internet\Plug-Ins. Linux: Check /usr/lib/flash-plugin or browser plugin directories. Android: Check Settings > Apps for Flash Player.
    Affected if Adobe Flash Player is present on the system
  2. Determine installed Flash Player version
    Windows: Run 'FlashPlayerInspector.swf' from Adobe or check version via registry at HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion. Mac: Right-click Flash Player.plugin > Get Info. Linux: Run 'rpm -q flash-plugin' or 'dpkg -l | grep flash'. Alternatively, visit Adobe's version check page in a browser.
    Affected if Version is 13.0.0.259 or earlier, OR any of: 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
  3. Identify if Adobe AIR is installed
    Windows: Check Add/Remove Programs for 'Adobe AIR' or look in C:\Program Files\Adobe. Mac: Check /Applications for Adobe AIR Installer.app. Run 'air -version' in terminal if AIR SDK is installed.
    Affected if Adobe AIR runtime is present on the system
  4. Determine installed Adobe AIR version
    Windows: Check Add/Remove Programs details for Adobe AIR version number. Mac: Run 'ls /Library/Frameworks/Adobe AIR.framework/Versions' to find installed version. Check AIR application manifest files for version details.
    Affected if Version is 15.0.0.356 or earlier (any version up to and including 15.0.0.356)
  5. Identify if Adobe AIR SDK or Compiler is installed
    Check for AIR SDK installation directory (commonly C:\Program Files\Adobe\AIR SDK or ~/AIR_SDK). Run 'adt -version' from SDK bin folder to get SDK version. Look for readme or version file in SDK root directory.
    Affected if Adobe AIR SDK or AIR SDK and Compiler version is 15.0.0.356 or earlier

The environment is affected if Adobe Flash Player matches any of the specific vulnerable versions listed, or if Adobe AIR, AIR SDK, or AIR SDK and Compiler is version 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+/16.0.0.257+ (Win/OSX), 11.2.202.429+ (Linux), and Adobe AIR to 16.0.0.245+ (Win/OSX) or 16.0.0.272+ (Android/SDK).

Recommended fix High confidence

Flash Player: 16.0.0.257+ (Windows/OS X), 11.2.202.429+ (Linux); Adobe AIR: 16.0.0.245+ (Windows/OS X), 16.0.0.272+ (Android); Adobe AIR SDK/Compiler: 16.0.0.272+

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to About Flash Player in the Help menu, or visit the Adobe version check page.
  2. 2. Identify the currently installed Adobe AIR version from the Windows Control Panel or Mac Applications folder.
  3. 3. For Flash Player: Navigate to https://get.adobe.com/flashplayer/ and download the latest version (16.0.0.257 or later for Windows/OS X, 11.2.202.429 or later for Linux).
  4. 4. For Adobe AIR: Navigate to https://get.adobe.com/air/ and download version 16.0.0.245 or later for Windows/OS X, or 16.0.0.272 or later for Android.
  5. 5. Close all browsers and applications that use Flash Player or AIR before running the installer.
  6. 6. Run the installer with administrative privileges and follow the prompts.
  7. 7. After installation, restart browsers and verify the new version matches the fixed release numbers.
Caveat Upgrading Flash Player from version 14.x to 16.x may introduce compatibility issues with older web applications; test in non-production environment first

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-0306 — 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-0306 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