Adobe Air Sdk And CompilerApplication · Adobe

CVE-2015-0305

HIGH · 9.3 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

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 by leveraging an unspecified "type confusion."

Technical summary

dbcve analysis · high confidence

This is a type confusion vulnerability in Adobe Flash Player and AIR that allows remote attackers to execute arbitrary code. The vulnerability stems from the software improperly handling object type references, leading to memory corruption that can be leveraged for code execution.

MitigationUpdate Adobe Flash Player to version 13.0.0.260 or later (14.x-16.x to 16.0.0.257 or later on Windows/OS X, 11.2.202.429 or later on Linux), and Adobe AIR to 16.0.0.245 or later (Windows/OS X) or 16.0.0.272 or later (Android). Alternatively, disable Flash Player or implement click-to-play policies if immediate updating is not feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Adobe Air Sdk And CompilerApplication

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 AirApplication

Affected:<= 15.0.0.356

Adobe Air SdkApplication

Affected:<= 15.0.0.356

CVSS breakdown

From the vector

Attack vector: Network
Complexity: M
Authentication: None
Confidentiality: Complete
Integrity: Complete
Availability: Complete

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Flash Player version

Open a web browser and navigate to a Flash version detection page (such as adobe.com/software/flash/about), or check the Flash Player DLL file properties (flash*.ocx or NPSWF32.dll) in the browser's plugin directory or system32 folder

Affected if The detected version is 11.2.202.425 or earlier, 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, or 15.0.0.238
Identify installed Adobe AIR version

Open the Adobe AIR application via Start menu (if installed) and check the Help > About Adobe AIR dialog, or locate the AIR application info in Add/Remove Programs (Windows) or Application folder (Mac)

Affected if The installed Adobe AIR version is 15.0.0.356 or any earlier version
Identify installed Adobe AIR SDK or Compiler version

Check the SDK version file (version.xml or similar) within the AIR SDK installation directory, or run 'adl -version' from the SDK bin folder if available

Affected if The AIR SDK or Compiler version is 15.0.0.356 or earlier
Check for browser plugin presence

In each installed web browser, navigate to the plugins or extensions settings page (for example, enter 'chrome://plugins' in Chrome address bar) and locate the Flash Player entry

Affected if Flash Player plugin is present and the version matches the affected Flash Player versions listed above

You are affected if any installed Adobe Flash Player, Adobe AIR, or AIR SDK version falls within or below the affected ranges specified for this CVE.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 15.0.0.356

Interim mitigation

Update Adobe Flash Player to version 13.0.0.260 or later (14.x-16.x to 16.0.0.257 or later on Windows/OS X, 11.2.202.429 or later on Linux), and Adobe AIR to 16.0.0.245 or later (Windows/OS X) or 16.0.0.272 or later (Android). Alternatively, disable Flash Player or implement click-to-play policies if immediate updating is not feasible.

Recommended fix High confidence

Flash Player: 13.0.0.260+ or 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: 16.0.0.272+

1. Identify the specific Adobe product installed (Flash Player, Adobe AIR, or AIR SDK & Compiler) and its current version number.
2. For Flash Player on Windows or OS X: Upgrade to version 13.0.0.260 or later, OR upgrade 14.x/15.x/16.x versions to 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 or 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 and AIR SDK & Compiler: Upgrade to version 16.0.0.272 or later.
7. Download updates from the official Adobe product page: https://helpx.adobe.com/flash-player.html (for Flash Player) or https://helpx.adobe.com/air.html (for AIR).
8. Install the updated version and verify the new version number matches the fixed release.

Caveat Adobe Flash Player reached end-of-life in December 2020; consider migrating away from Flash-based applications as no further security updates will be available

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

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0305 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-0305?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 15.0.0.356 or later

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 6.1%

Affects: Adobe Air Sdk And Compiler

Remediation

A high-priority fix

Fix this in Adobe Air Sdk And Compiler 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2015-0305 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References