dbcve.org
AirApplication · Adobe

CVE-2015-7635

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-7636, CVE-2015-7637, CVE-2015-7638, CVE-2015-7639, 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 allowing remote attackers to execute arbitrary code via unspecified vectors. The flaw exists in memory management where freed memory is accessed after being deallocated, potentially enabling code execution.

MitigationUpdate Adobe Flash Player to version 18.0.0.252/19.0.0.207 or later (11.2.202.535 on Linux) and Adobe AIR to 19.0.0.213 or later. Given Flash EOL, consider removing Flash Player entirely if no longer needed.

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 on Windows
    Open Control Panel > Programs and Features, look for 'Adobe Flash Player XX' entry, or run 'powershell Get-ItemProperty "C:\Windows\System32\Macromed\Flash\*' to list Flash DLL versions
    Affected if Version is 19.0.0.185 or earlier, or 11.2.202.521 or earlier on the 11.2.x branch
  2. Check Adobe Flash Player version on Linux
    Run 'rpm -q flash-player' or check /usr/lib/flash-plugin/ directory, or verify via browser plugin about:plugins
    Affected if Version is 11.2.202.521 or earlier
  3. Check Adobe AIR version
    Open Control Panel > Programs and Features for Windows, or run 'air -version' from AIR SDK bin directory, or check /Applications on macOS
    Affected if Version is 19.0.0.190 or earlier (Air, Air SDK, or Air SDK & Compiler)
  4. Verify Flash Player active plugin in browsers
    In Internet Explorer, check Manage Add-ons for 'Shockwave Flash Object'; in Chrome, navigate to chrome://plugins and locate Flash; in Firefox, navigate to about:addons and check Plugins
    Affected if Installed Flash plugin version matches affected versions listed above

You are affected if Adobe Flash Player (any browser plugin) is version 19.0.0.185 or earlier, or 11.2.202.521 or earlier, or if Adobe AIR is version 19.0.0.190 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.190
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 18.0.0.252/19.0.0.207 or later (11.2.202.535 on Linux) and Adobe AIR to 19.0.0.213 or later. Given Flash EOL, consider removing Flash Player entirely if no longer needed.

Recommended fix High confidence

Adobe Flash Player 18.0.0.252/19.0.0.207/11.2.202.535 (Linux), Adobe AIR 19.0.0.213, Adobe AIR SDK 19.0.0.213, Adobe AIR SDK & Compiler 19.0.0.213

  1. 1. Identify all systems running Adobe Flash Player, Adobe AIR, Adobe AIR SDK, or Adobe AIR SDK & Compiler
  2. 2. Check current version on each system using the Adobe Version Checker or system inventory tools
  3. 3. For Flash Player: upgrade to version 18.0.0.252 (or 19.0.0.207 for the 19.x branch) on Windows/OS X, or 11.2.202.535 on Linux
  4. 4. For Adobe AIR: upgrade to version 19.0.0.213
  5. 5. For Adobe AIR SDK: upgrade to version 19.0.0.213
  6. 6. For Adobe AIR SDK & Compiler: upgrade to version 19.0.0.213
  7. 7. Obtain upgrades from the official Adobe security bulletin at https://helpx.adobe.com/security/products/flash-player/apsb15-25.html
  8. 8. Deploy the updated versions across all affected systems
Caveat This is a security upgrade; ensure compatibility testing with existing Flash-based applications before deploying in production environments

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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