dbcve.org
AirApplication · Adobe

CVE-2015-7639

HIGH · 10.0 CVSS v2.0 Published 2015-10-18
Fix available
A fix is available. Upgrade to after 19.0.0.190 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
Use-after-free vulnerability in Adobe Flash Player before 18.0.0.252 and 19.x before 19.0.0.207 on Windows and OS X and before 11.2.202.535 on Linux, Adobe AIR before 19.0.0.213, Adobe AIR SDK before 19.0.0.213, and Adobe AIR SDK & Compiler before 19.0.0.213 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-7629, CVE-2015-7631, CVE-2015-7635, CVE-2015-7636, CVE-2015-7637, CVE-2015-7638, CVE-2015-7640, CVE-2015-7641, CVE-2015-7642, CVE-2015-7643, and CVE-2015-7644.

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 Adobe AIR that allows remote attackers to execute arbitrary code via unspecified vectors. The flaw involves improper memory management where memory is accessed after being freed, potentially leading to code execution.

MitigationUpdate Adobe Flash Player to version 18.0.0.252 or later (19.x to 19.0.0.207 or later) and Adobe AIR to version 19.0.0.213 or later. Consider removing or disabling 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:<= 19.0.0.190
Air SdkApplication
Affected:<= 19.0.0.190
Air Sdk \& CompilerApplication
Affected:<= 19.0.0.190
Flash PlayerApplication
Affected:<= 19.0.0.185<= 11.2.202.521

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 Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion (32-bit) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer\CurrentVersion (64-bit). Note the Version string value.
    Affected if The version is 19.0.0.185 or lower, or 11.2.202.521 or lower (11.x branch)
  2. Check Adobe Flash Player version in browsers
    In Internet Explorer, open Tools > Manage Add-ons and select Shockwave Flash Object to view the version. In Chrome, navigate to chrome://components/ and find the Flash entry. In Firefox, open Add-ons > Plugins and locate the Shockwave Flash entry.
    Affected if The displayed version is 19.0.0.185 or lower, or 11.2.202.521 or lower (11.x branch)
  3. Check Adobe AIR version on the system
    On Windows, open Programs and Features (or Add/Remove Programs) and locate Adobe AIR in the installed programs list. Note the version shown. Alternatively, search for the file 'airappinstaller.exe' in the Adobe AIR folder and view its file properties.
    Affected if The version is 19.0.0.190 or lower

The system is affected if Adobe Flash Player version is 19.0.0.185 or lower (or 11.2.202.521 or lower for 11.x branch) or Adobe AIR version is 19.0.0.190 or lower.

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

Update Adobe Flash Player to version 18.0.0.252 or later (19.x to 19.0.0.207 or later) and Adobe AIR to version 19.0.0.213 or later. Consider removing or disabling Flash Player if not required.

Recommended fix High confidence

Adobe Flash Player 19.0.0.207 (or 18.0.0.252 for 18.x branch), 11.2.202.535 for Linux; Adobe AIR 19.0.0.213

  1. 1. Identify the installed Adobe product (Flash Player, AIR, AIR SDK, or AIR SDK & Compiler) and its current version
  2. 2. For Flash Player 18.x users on Windows/OS X: upgrade to version 18.0.0.252
  3. 3. For Flash Player 19.x users on Windows/OS X: upgrade to version 19.0.0.207
  4. 4. For Flash Player 11.x users on Linux: upgrade to version 11.2.202.535
  5. 5. For Adobe AIR users: upgrade to version 19.0.0.213
  6. 6. For Adobe AIR SDK users: upgrade to version 19.0.0.213
  7. 7. For Adobe AIR SDK & Compiler users: upgrade to version 19.0.0.213
  8. 8. Verify the installation of the patched version
Caveat Flash Player reached end-of-life in December 2020; consider migrating away from Flash-based technologies

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

Fix this in Air Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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