dbcve.org
Adobe AirApplication · Adobe

CVE-2015-0303

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

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 or denial of service via unspecified vectors. Affects specific versions across Windows, OS X, Linux, and Android platforms.

MitigationUpdate Adobe Flash Player to version 13.0.0.260, 16.0.0.257, or later (or 11.2.202.429 on Linux); update Adobe AIR to 16.0.0.245 or later (16.0.0.272 on Android). Consider Flash removal given EOL status.

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 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
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. Check Adobe Flash Player version on Windows
    Open a browser and navigate to 'about:flash' in the URL bar, or visit the Adobe Flash Player version check page at https://www.adobe.com/software/flash/about/. Alternatively, open Control Panel > Programs and Features to see installed Adobe Flash Player entries.
    Affected if The displayed version matches 11.2.202.425, any version <= 13.0.0.259, or 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, or 15.0.0.238.
  2. Check Adobe Flash Player version on macOS
    Open System Information (from the Apple menu > About This Mac > System Report), then look under Software > Plugins for Adobe Flash Player. Or check /Library/Application Support/Adobe/Flash Player for installed components.
    Affected if The displayed version matches any of the affected versions listed in step 1.
  3. Check Adobe Flash Player version on Linux
    Use the package manager (dpkg -l | grep flash or rpm -qa | grep flash) or check the Flash Player plugin in the browser's add-ons manager.
    Affected if The installed version is 11.2.202.425 or any version <= 13.0.0.259.
  4. Check Adobe AIR version
    On Windows, open Control Panel > Programs and Features and look for Adobe AIR. On macOS, check /Applications for Adobe AIR or use System Information > Software > Applications. On Linux, use the package manager (dpkg -l | grep -i air).
    Affected if The installed Adobe AIR version is 15.0.0.356 or any earlier version (<= 15.0.0.356).
  5. Check Adobe AIR SDK or AIR SDK and Compiler version
    If installed as part of development tools, check the SDK directory or look in Add/Remove Programs for Adobe AIR SDK entries.
    Affected if The installed SDK version is 15.0.0.356 or any earlier version (<= 15.0.0.356).

A user is affected if Adobe Flash Player is installed with any of the specific affected versions listed, or if Adobe AIR/SDK is installed at version 15.0.0.356 or lower.

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, or later (or 11.2.202.429 on Linux); update Adobe AIR to 16.0.0.245 or later (16.0.0.272 on Android). Consider Flash removal given EOL status.

Recommended fix High confidence

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

  1. 1. Identify all systems with Adobe Flash Player installed and note the current version.
  2. 2. For Windows and OS X: Upgrade Flash Player to version 16.0.0.257 or later.
  3. 3. For Windows and OS X: If using Flash Player 13.x branch, upgrade to version 13.0.0.260 or later.
  4. 4. For Linux: Upgrade Flash Player to version 11.2.202.429 or later.
  5. 5. For Adobe AIR (Windows/OS X): Upgrade to version 16.0.0.245 or later.
  6. 6. For Adobe AIR (Android): Upgrade to version 16.0.0.272 or later.
  7. 7. For Adobe AIR SDK: Upgrade to version 16.0.0.272 or later.
  8. 8. For Adobe AIR SDK & Compiler: Upgrade to version 16.0.0.272 or later.
Caveat Flash Player 16.x is the final major release as Adobe ended Flash Player support; ensure compatibility with legacy content

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

Fix this in Adobe Air Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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