dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-0302

MEDIUM · 5.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 →
59/100
Remediation priority · Elevated
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 allow attackers to obtain sensitive keystroke information via unspecified 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 and AIR contain a vulnerability that allows attackers to obtain sensitive keystroke information via unspecified vectors. The vulnerability affects multiple versions across Windows, OS X, Linux, and Android platforms, and extends to the AIR SDK and AIR SDK & Compiler products.

MitigationUpdate Adobe Flash Player to version 13.0.0.260, 16.0.0.257, or 11.2.202.429 (depending on branch/platform), and update Adobe AIR to version 16.0.0.245 or 16.0.0.272 (platform-dependent), and AIR SDK to 16.0.0.272.

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:= 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
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
Partial
Integrity
None
Availability
None

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

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 product
    Check if Adobe Flash Player, Adobe AIR, AIR SDK, or AIR SDK & Compiler is installed on the system. On Windows, look in Program Files/Program Files (x86) for Adobe folders, or check browser plugins for Flash. For AIR SDK, check the installation directory.
    Affected if Any of these Adobe products are installed on the system
  2. Determine Flash Player version in browsers
    In each installed browser, navigate to the Adobe version check page (about:flash or use the Adobe Flash Player Help > About page), or check the browser's plugin/add-on list for the Flash Player plugin version.
    Affected if The Flash Player version is 11.2.202.425, or any version <= 13.0.0.259, or 14.0.0.125/145/176/179, or 15.0.0.144/152/167/189/223/238
  3. Check Adobe AIR runtime version
    On Windows, open Programs and Features or the Adobe AIR application itself and look for the version information. On macOS, check /Applications/Adobe AIR or use Get Info on the application.
    Affected if Adobe AIR version is <= 15.0.0.356
  4. Check AIR SDK version
    If using Adobe AIR SDK for development, locate the SDK directory and check the version file or readme, or run the AIR SDK compiler with a version flag. Common locations include C:\Program Files\Adobe\AIR SDK or /opt/AIR_SDK.
    Affected if AIR SDK version is <= 15.0.0.356
  5. Check AIR SDK & Compiler version
    If using the AIR SDK combined with Compiler package, check the version metadata in the SDK installation folder or run the compiler with a version query parameter.
    Affected if AIR SDK & Compiler version is <= 15.0.0.356

The environment is affected if any installed Adobe Flash Player version is 11.2.202.425, <=13.0.0.259, 14.0.0.x series (125/145/176/179), or 15.0.0.x series (144/152/167/189/223/238); or if Adobe AIR, AIR SDK, or AIR SDK & Compiler is at version <=15.0.0.356.

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.

From vendor data
Upgrade available Upgrade to a release after 15.0.0.356
Interim mitigation

Update Adobe Flash Player to version 13.0.0.260, 16.0.0.257, or 11.2.202.429 (depending on branch/platform), and update Adobe AIR to version 16.0.0.245 or 16.0.0.272 (platform-dependent), and AIR SDK to 16.0.0.272.

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