dbcve.org
AirApplication · Adobe

CVE-2015-4432

HIGH · 10.0 CVSS v2.0 Published 2015-07-09
Fix available
A fix is available. Upgrade to after 18.0.0.144 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
Heap-based buffer overflow in Adobe Flash Player before 13.0.0.302 and 14.x through 18.x before 18.0.0.203 on Windows and OS X and before 11.2.202.481 on Linux, Adobe AIR before 18.0.0.180, Adobe AIR SDK before 18.0.0.180, and Adobe AIR SDK & Compiler before 18.0.0.180 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-3135 and CVE-2015-5118.

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

Heap-based buffer overflow vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code via unspecified vectors. The flaw exists in the processing of unspecified data, causing memory corruption that can be leveraged for code execution.

MitigationUpdate Adobe Flash Player to version 13.0.0.302 or later (Windows/OS X), 11.2.202.481 or later (Linux), or 18.0.0.203 or later for the 14.x-18.x branch. Also update Adobe AIR and AIR SDK to version 18.0.0.180 or later. Alternatively, disable or remove Flash Player if not required.

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.144
Air SdkApplication
Affected:<= 18.0.0.144
Air Sdk \& CompilerApplication
Affected:<= 18.0.0.144
Flash PlayerApplication
Affected:<= 11.2.202.468<= 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

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 if Adobe Flash Player is installed
    On Windows, check the file version of NPSWF32.dll (Firefox), Flash.ocx (IE), or PepperFlash (Chrome) in the browser plugin directories. On Mac, check /Library/Internet Plug-Ins/Flash Player.plugin. On Linux, check /usr/lib/flash-plugin/ or /usr/lib64/flash-plugin/. Use 'file --version' or right-click properties to obtain version information.
    Affected if The installed version matches any of these affected versions: 11.2.202.468 or earlier; 13.0.0.289 or earlier; any of 14.0.0.125, 14.0.0.145, 14.0.0.176, 14.0.0.179; any of 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, 15.0.0.246.
  2. Check if Adobe AIR is installed
    On Windows, look for Adobe AIR in Add/Remove Programs or check C:\Program Files (x86)\Adobe\Adobe AIR\versions\. On Mac, check /Applications/Adobe AIR Installer.app. Determine the installed version from the directory name or installer properties.
    Affected if The installed Adobe AIR version is 18.0.0.144 or earlier.
  3. Check Adobe AIR SDK version
    If you develop AIR applications, locate the AIR SDK directory (often in your IDE or a standalone SDK folder). Open the readme or version file within the SDK directory, or run 'adt -version' if the AIR Developer Tool is available.
    Affected if The AIR SDK or AIR SDK & Compiler version is 18.0.0.144 or earlier.
  4. Verify if Flash Player browser plugin is enabled
    Open your web browser's add-on or extension manager. In Firefox, go to Add-ons > Plugins. In Chrome, go to chrome://plugins. In IE, go to Manage Add-ons. Check if the Shockwave Flash Object is enabled.
    Affected if The Flash Player plugin is enabled and the version falls within the affected ranges listed above.

You are affected if Adobe Flash Player (browser plugin or standalone) or Adobe AIR/AIR SDK version falls within the specified vulnerable version ranges and the affected component is installed and enabled.

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

Update Adobe Flash Player to version 13.0.0.302 or later (Windows/OS X), 11.2.202.481 or later (Linux), or 18.0.0.203 or later for the 14.x-18.x branch. Also update Adobe AIR and AIR SDK to version 18.0.0.180 or later. Alternatively, disable or remove Flash Player if not required.

Recommended fix High confidence

Flash Player 13.0.0.302/18.0.0.203 (Windows/OS X), 11.2.202.481 (Linux); Adobe AIR/AIR SDK 18.0.0.180

  1. 1. Identify the installed Adobe Flash Player or AIR version by navigating to 'About Flash Player' or checking system settings
  2. 2. Download the appropriate patched version from the Adobe security bulletin at https://helpx.adobe.com/security/products/flash-player/apsb15-16.html
  3. 3. For Flash Player on Windows/OS X: Upgrade to version 13.0.0.302 or 18.0.0.203 (whichever matches your license/requirement)
  4. 4. For Flash Player on Linux: Upgrade to version 11.2.202.481
  5. 5. For Adobe AIR: Upgrade to version 18.0.0.180
  6. 6. For Adobe AIR SDK or AIR SDK & Compiler: Upgrade to version 18.0.0.180
  7. 7. Restart any browsers or applications using Flash Player after installation
  8. 8. Verify the installed version matches the expected patched version
Caveat Flash Player 13.x and later require sandboxing changes; some legacy content may require modification

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

Fix this in Air Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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