dbcve.org
AirApplication · Adobe

CVE-2015-8418

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-8419, CVE-2015-8443, 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 · high confidence

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution or denial of service. The vulnerability exists in unspecified vectors within the affected versions across Windows, OS X, and Linux platforms.

MitigationUpgrade Adobe Flash Player to version 18.0.0.268, 20.0.0.228 (for 19.x/20.x), or 11.2.202.554 (Linux), and Adobe AIR/SDK to version 20.0.0.204 to address the memory corruption flaw.

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
AirApplication
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
Air SdkApplication
Affected:<= 19.0.0.241
Air Sdk \& CompilerApplication
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 on Windows
    Open Control Panel > Programs and Features, find Adobe Flash Player in the list, and note the version column. Alternatively, visit https://helpx.adobe.com/flash-player.html or create a test file with 'http://www.adobe.com/software/flash/about/' links to display version info.
    Affected if The installed version is 11.2.202.548 or earlier, 18.0.0.261 or earlier, or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245
  2. Check Adobe Flash Player version on macOS
    Open System Preferences > Flash Player (if installed), or navigate to /Library/Application Support/Adobe/Flash Player and check the version info. You can also right-click any SWF file and select 'Get Info' to see the version.
    Affected if The installed version is 11.2.202.548 or earlier, 18.0.0.261 or earlier, or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245
  3. Check Adobe Flash Player version on Linux
    Open a terminal and run: rpm -q flash-player or dpkg -l | grep flash. Alternatively, open the Adobe Flash Player Settings manager in a browser.
    Affected if The installed version is 11.2.202.548 or earlier, 18.0.0.261 or earlier, or exactly 19.0.0.185, 19.0.0.207, 19.0.0.226, or 19.0.0.245
  4. Check Adobe AIR version
    Open Control Panel (Windows) or Applications folder (macOS), look for Adobe AIR in installed programs. On Windows, run 'airpackage -version' from AIR SDK bin folder, or check the version in Add/Remove Programs.
    Affected if The installed version is 19.0.0.241 or earlier
  5. Check Adobe AIR SDK version
    Navigate to the AIR SDK installation directory and locate the version file, or run 'airc -version' from the bin folder. On Windows, check the version via Programs and Features if the SDK is registered as installed software.
    Affected if The installed SDK version is 19.0.0.241 or earlier

You are affected if Adobe Flash Player is any version <= 11.2.202.548, <= 18.0.0.261, or exactly 19.0.0.185/207/226/245; or if Adobe AIR/SDK is version 19.0.0.241 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 19.0.0.241
Vendor patch helpx.adobe.com →
Interim mitigation

Upgrade Adobe Flash Player to version 18.0.0.268, 20.0.0.228 (for 19.x/20.x), or 11.2.202.554 (Linux), and Adobe AIR/SDK to version 20.0.0.204 to address the memory corruption flaw.

Recommended fix High confidence

Flash Player 20.0.0.228 (or 18.0.0.268 for 18.x line); Adobe AIR 20.0.0.204; Adobe AIR SDK 20.0.0.204; Adobe AIR SDK & Compiler 20.0.0.204

  1. 1. Identify the installed Adobe Flash Player version by navigating to https://helpx.adobe.com/flash-player.html and checking the version displayed
  2. 2. Identify the installed Adobe AIR version from Programs and Features (Windows) or /Library/Application Support/Adobe/AIR (Mac)
  3. 3. For Flash Player: Download the fixed version 20.0.0.228 or later from https://get.adobe.com/flashplayer/
  4. 4. For Adobe AIR: Download the fixed version 20.0.0.204 or later from https://get.adobe.com/air/
  5. 5. For Adobe AIR SDK/SDK & Compiler: Download version 20.0.0.204 or later from https://airsdk.harman.com/ (if using older versions) or Adobe's AIR SDK download page
  6. 6. Uninstall the existing Flash Player and AIR installations before installing the fixed versions
  7. 7. Restart any browsers after upgrading Flash Player
  8. 8. Verify the installed versions match the fixed releases (Flash Player 20.0.0.228+ or 18.0.0.268+, AIR 20.0.0.204+)
Caveat Upgrading Flash Player and AIR to version 20.x may drop support for older content or require re-testing of AIR applications; however, this security fix is critical and should be applied regardless

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

Fix this in Air Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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