AirApplication · Adobe

CVE-2015-8046

HIGH · 10.0 CVSS v2.0 Published 2015-11-11
Fix available
A fix is available. Upgrade to after 19.0.0.213 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Use-after-free vulnerability in Adobe Flash Player before 18.0.0.261 and 19.x before 19.0.0.245 on Windows and OS X and before 11.2.202.548 on Linux, Adobe AIR before 19.0.0.241, Adobe AIR SDK before 19.0.0.241, and Adobe AIR SDK & Compiler before 19.0.0.241 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-7651, CVE-2015-7652, CVE-2015-7653, CVE-2015-7654, CVE-2015-7655, CVE-2015-7656, CVE-2015-7657, CVE-2015-7658, CVE-2015-7660, CVE-2015-7661, CVE-2015-7663, CVE-2015-8042, CVE-2015-8043, and CVE-2015-8044.

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

Use-after-free vulnerability in Adobe Flash Player and AIR allowing arbitrary code execution. The vulnerability occurs when memory is accessed after it has been freed, potentially enabling attackers to execute arbitrary code via unspecified vectors.

MitigationUpdate Adobe Flash Player to 18.0.0.261+/19.0.0.245+ (Windows/OS X) or 11.2.202.548+ (Linux), and Adobe AIR to 19.0.0.241+. Note: Adobe Flash Player reached end-of-life in December 2020; consider migrating away from Flash-based applications entirely.

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.213<= 19.0.0.190
Air SdkApplication
Affected:<= 19.0.0.213
Air Sdk \& CompilerApplication
Affected:<= 19.0.0.213
Flash PlayerApplication
Affected:<= 18.0.0.255= 19.0.0.185= 19.0.0.207= 19.0.0.226<= 11.2.202.540

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 Flash Player version on Windows
    Open a browser and navigate to 'about:flash' in the address bar, or check the Windows registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion
    Affected if The displayed version is 18.0.0.255 or earlier, 19.0.0.185, 19.0.0.207, 19.0.0.226, or 11.2.202.540 or earlier
  2. Check Flash Player version on macOS
    Open a terminal and run: defaults read /Library/Internet\ Plug-Ins/FlashPlayer.plugin/Contents/Info CFBundleVersion, or navigate to /Library/Internet Plug-Ins/ and inspect the FlashPlayer.plugin info
    Affected if The version matches 18.0.0.255 or earlier, 19.0.0.185, 19.0.0.207, 19.0.0.226, or 11.2.202.540 or earlier
  3. Check Flash Player version on Linux
    Run the command: rpm -q flash-player or dpkg -l | grep -i flash, or inspect /usr/lib/flash-plugin/libflashplayer.so
    Affected if The installed version is 11.2.202.540 or earlier
  4. Check Adobe AIR version on Windows
    Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR, or check the AIR version via the AIR application properties
    Affected if The installed version is 19.0.0.213 or earlier, or 19.0.0.190 or earlier
  5. Check Adobe AIR SDK version
    If using Adobe AIR SDK for development, check the version file in the SDK installation directory (typically version.xml or the SDK readme)
    Affected if The SDK version is 19.0.0.213 or earlier

If any installed Adobe Flash Player or AIR version matches the affected ranges (18.0.0.255 or lower, specific 19.x versions, or 11.2.202.540 or lower), the environment is vulnerable to this use-after-free flaw.

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

Update Adobe Flash Player to 18.0.0.261+/19.0.0.245+ (Windows/OS X) or 11.2.202.548+ (Linux), and Adobe AIR to 19.0.0.241+. Note: Adobe Flash Player reached end-of-life in December 2020; consider migrating away from Flash-based applications entirely.

Recommended fix High confidence

Flash Player 18.0.0.261+ / 19.0.0.245+ / 11.2.202.548+ (Linux); Adobe AIR 19.0.0.241+; Adobe AIR SDK 19.0.0.241+

  1. 1. Identify the installed Adobe Flash Player version by navigating to about:flash (in URL bar) or checking the system control panel
  2. 2. Identify the installed Adobe AIR version from Add/Remove Programs or the AIR application properties
  3. 3. Download the fixed version from the official Adobe security bulletin (apsb15-28) or Adobe's download center
  4. 4. For Flash Player: Upgrade to version 18.0.0.261 or later (Windows/OS X), 11.2.202.548 or later (Linux), or 19.0.0.245 or later for the 19.x branch
  5. 5. For Adobe AIR: Upgrade to version 19.0.0.241 or later
  6. 6. For Adobe AIR SDK: Upgrade to version 19.0.0.241 or later
  7. 7. Restart any browsers or applications using Flash Player or AIR
  8. 8. Verify the installed version matches or exceeds the fixed versions listed above
Caveat Adobe Flash Player and AIR are end-of-life products; ensure compatibility with any legacy applications that depend on these runtimes

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

Fix this in Air 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-8046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-8046 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