dbcve.org
Air SdkApplication · Adobe

CVE-2015-8443

HIGH · 10.0 CVSS v2.0 Published 2015-12-10
Fix available
A fix is available. Upgrade to after 19.0.0.241 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 18.0.0.268 and 19.x and 20.x before 20.0.0.228 on Windows and OS X and before 11.2.202.554 on Linux, Adobe AIR before 20.0.0.204, Adobe AIR SDK before 20.0.0.204, and Adobe AIR SDK & Compiler before 20.0.0.204 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-8045, CVE-2015-8047, CVE-2015-8060, CVE-2015-8408, CVE-2015-8416, CVE-2015-8417, CVE-2015-8418, CVE-2015-8419, CVE-2015-8444, CVE-2015-8451, and CVE-2015-8455.

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 · moderate confidence

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution or denial of service. The vulnerability affects specific older versions across Windows, OS X, and Linux platforms.

MitigationUpdate Adobe Flash Player to version 18.0.0.268, 20.0.0.228 (or 11.2.202.554 on Linux), and Adobe AIR to 20.0.0.204 or later. Consider migrating away from Flash as it reaches end-of-life.

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
Air SdkApplication
Affected:<= 19.0.0.241
Air Sdk \& CompilerApplication
Affected:<= 19.0.0.241
Flash PlayerApplication
Affected:<= 11.2.202.548<= 18.0.0.261= 19.0.0.185= 19.0.0.207= 19.0.0.226= 19.0.0.245
AirApplication
Affected:<= 19.0.0.241

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 in Windows
    Open Windows Explorer and navigate to the Flash Player installation directory (typically C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash). Right-click on flash.ocx or NPSWF32.dll, select Properties, and view the File Version tab.
    Affected if The file version is <= 11.2.202.548, <= 18.0.0.261, 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245
  2. Check Adobe Flash Player version via browser
    In Internet Explorer, navigate to Tools > Manage Add-ons > Shockwave Flash Object and note the version. In Chrome, type chrome://plugins in the address bar and locate Flash. In Firefox, type about:plugins in the address bar.
    Affected if The displayed Flash Player version matches any of the affected versions listed above.
  3. Check Adobe Flash Player version on Linux
    Navigate to /usr/lib/flash-plugin or /usr/lib64/flash-plugin (depending on architecture) and run 'rpm -q flash-plugin' or check the version of libflashplayer.so using 'ls -la'.
    Affected if The version is <= 11.2.202.548 (Linux-specific threshold)
  4. Check Adobe AIR version on Windows
    Open Control Panel > Programs and Features (or Add or Remove Programs on older Windows). Look for Adobe AIR in the list and note the version column.
    Affected if The installed version is <= 19.0.0.241
  5. Check Adobe AIR SDK version
    If using the AIR SDK for development, open the AIR SDK readme.txt or version.xml file located in the SDK installation directory, or run 'air -version' from the command line if available.
    Affected if The SDK version is <= 19.0.0.241

You are affected if Adobe Flash Player or Adobe AIR is installed with any version <= 19.0.0.241, or if Flash Player matches the specific affected 19.x versions (185, 207, 226, 245) or 11.2.x versions <= 548.

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 19.0.0.241
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 18.0.0.268, 20.0.0.228 (or 11.2.202.554 on Linux), and Adobe AIR to 20.0.0.204 or later. Consider migrating away from Flash as it reaches end-of-life.

Recommended fix High confidence

Adobe Flash Player 18.0.0.268+/20.0.0.228+ (11.2.202.554+ for Linux); Adobe AIR 20.0.0.204+; Adobe AIR SDK 20.0.0.204+; Adobe AIR SDK & Compiler 20.0.0.204+

  1. 1. Identify all systems with Adobe Flash Player installed and note the current version.
  2. 2. Identify all systems with Adobe AIR, AIR SDK, or AIR SDK & Compiler installed and note the current version.
  3. 3. For Flash Player on Windows and OS X: Upgrade to version 18.0.0.268 or later (for 18.x), or version 20.0.0.228 or later (for 19.x/20.x).
  4. 4. For Flash Player on Linux: Upgrade to version 11.2.202.554 or later.
  5. 5. For Adobe AIR: Upgrade to version 20.0.0.204 or later.
  6. 6. For Adobe AIR SDK: Upgrade to version 20.0.0.204 or later.
  7. 7. For Adobe AIR SDK & Compiler: Upgrade to version 20.0.0.204 or later.
  8. 8. Verify the installed versions match or exceed the fixed releases after patching.
Caveat Adobe Flash Player is end-of-life and no longer receives security updates; migrating to alternative technologies is strongly recommended

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

Fix this in Air Sdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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