dbcve.org
AirApplication · Adobe

CVE-2015-5575

HIGH · 10.0 CVSS v2.0 Published 2015-09-22
Fix available
A fix is available. Upgrade to after 18.0.0.199 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.241 and 19.x before 19.0.0.185 on Windows and OS X and before 11.2.202.521 on Linux, Adobe AIR before 19.0.0.190, Adobe AIR SDK before 19.0.0.190, and Adobe AIR SDK & Compiler before 19.0.0.190 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-5577, CVE-2015-5578, CVE-2015-5580, CVE-2015-5582, CVE-2015-5588, and CVE-2015-6677.

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 AIR allowing arbitrary code execution or denial of service via unspecified vectors, affecting multiple versions across Windows, OS X, and Linux platforms.

MitigationDeploy the vendor-patched versions (Flash Player 18.0.0.241/19.0.0.185 or 11.2.202.521 for Linux; AIR 19.0.0.190) to all affected endpoints and remove unused Flash installations.

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:<= 18.0.0.143<= 18.0.0.199
AndroidOperating system
Affected:all versions
Flash PlayerApplication
Affected:<= 13.0.0.289= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.152= 15.0.0.167= 15.0.0.189= 15.0.0.223= 15.0.0.239= 15.0.0.246= 16.0.0.235
Air SdkApplication
Affected:<= 18.0.0.199
Air Sdk \& CompilerApplication
Affected:<= 18.0.0.180

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 browsers
    Open a browser and navigate to 'about:plugin' (Firefox) or chrome://plugins (Chrome), or visit https://helpx.adobe.com/flash-player.html to detect the installed version. Alternatively, check the Flash Player DLL location: On Windows, examine C:\Windows\System32\Macromed\Flash\ or the browser plugin directory.
    Affected if The installed Flash Player version is 13.0.0.289 or earlier; equals any of 14.0.0.125, 14.0.0.145, 14.0.0.176, 14.0.0.179, 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, 15.0.0.246, or 16.0.0.235; or is 18.0.0.241 or earlier for version 18.x.
  2. Check Adobe AIR desktop runtime version
    On Windows, open Add or Remove Programs and look for 'Adobe AIR' or check the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AdobeAIR. On macOS, examine /Applications/Adobe AIR Application Installer.app or run 'ls /Applications | grep -i adobe'.
    Affected if The installed Adobe AIR version is 18.0.0.143 or earlier, or 18.0.0.199 or earlier.
  3. Check Adobe AIR SDK installation
    Look for the AIR SDK in the installation directory, commonly at C:\Program Files\Adobe\Adobe AIR SDK or on macOS at /Library/Application Support/Adobe/AIR. Check the 'versions.xml' or SDK readme for the exact version number.
    Affected if The installed AIR SDK version is 18.0.0.199 or earlier, or the AIR SDK & Compiler version is 18.0.0.180 or earlier.
  4. Check for Flash Player on Android devices
    On Android devices, navigate to Settings > Apps > All and look for 'Flash Player' in the application list, or check if any browser has the Flash plugin enabled.
    Affected if Adobe Flash Player is installed and enabled on any Android device (all versions are affected).

A system is affected if Adobe Flash Player, Adobe AIR, or the AIR SDK is installed and the installed version matches any of the vulnerable versions listed, or if Flash is present on Android.

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

Deploy the vendor-patched versions (Flash Player 18.0.0.241/19.0.0.185 or 11.2.202.521 for Linux; AIR 19.0.0.190) to all affected endpoints and remove unused Flash installations.

Recommended fix High confidence

Flash Player 19.0.0.185 (or 18.0.0.241); Adobe AIR 19.0.0.190; Adobe AIR SDK 19.0.0.190; Adobe AIR SDK & Compiler 19.0.0.190

  1. 1. Identify current Adobe Flash Player version by navigating to https://www.adobe.com/software/flash/about/ in a browser
  2. 2. Identify current Adobe AIR version by checking Help > About Adobe AIR in the application
  3. 3. For Flash Player: Download the fixed version from the official Adobe security bulletin APSB15-23 at https://helpx.adobe.com/security/products/flash-player/apsb15-23.html
  4. 4. For Adobe AIR: Download Adobe AIR 19.0.0.190 from the official Adobe website or the APSB15-23 bulletin
  5. 5. For Adobe AIR SDK/Compiler: Download version 19.0.0.190 from the Adobe AIR SDK download page
  6. 6. Close all browsers and applications using Flash Player before installation
  7. 7. Run the installer with administrator privileges
  8. 8. Restart browsers and verify the new version is installed
Caveat Flash Player reached end-of-life on December 31, 2020 and is no longer supported; consider migrating to HTML5 alternatives

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

Fix this in 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-5575 — 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-5575 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