CVE-2015-7644
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 · uneditedUse-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, and CVE-2015-7643.
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 confidenceUse-after-free vulnerability in Adobe Flash Player and Adobe AIR allowing remote attackers to execute arbitrary code. Affects Flash Player versions before 18.0.0.252/19.0.0.207 (Windows/OS X), before 11.2.202.535 (Linux), and AIR versions before 19.0.0.213. The vulnerability stems from improper memory management allowing freed memory to be accessed.
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<= 19.0.0.190<= 19.0.0.190<= 19.0.0.190<= 19.0.0.185<= 11.2.202.521CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows Flash Player versionOpen Control Panel > Programs and Features, look for 'Adobe Flash Player XX' entry, or open cmd.exe and run: reg query 'HKLM\SOFTWARE\Macromedia\FlashPlayer' /v VersionAffected if Version is 19.0.0.185 or lower, or 11.2.202.521 or lower on the 11.x branch for Linux
-
Check macOS Flash Player versionOpen System Preferences > Flash Player, or run in Terminal: /Library/Application\ Support/Adobe/Flash\ Player/install_flash_player_osx.app/Contents/MacOS/Install\ Adobe\ Flash\ Player --dumpversionAffected if Version is 19.0.0.185 or lower
-
Check Adobe AIR version on WindowsOpen Control Panel > Programs and Features, look for 'Adobe AIR' entry and note the version numberAffected if Version is 19.0.0.190 or lower
-
Check Adobe AIR version on macOSOpen Terminal and run: ls /Applications | grep -i 'Adobe AIR' then check the app's Info.plist or right-click the app > Get Info to view versionAffected if Version is 19.0.0.190 or lower
-
Identify if Flash is actively usedCheck browsers for enabled Flash plugins: in Chrome, navigate to chrome://plugins and look for 'Shockwave Flash', or in Firefox, navigate to about:addons > PluginsAffected if Adobe Flash Player plugin is present and enabled with a version matching the affected ranges above
You are affected if Adobe Flash Player version is 19.0.0.185 or lower (or 11.2.202.521 or lower on Linux) OR Adobe AIR version is 19.0.0.190 or lower, and the Flash/ AIR component is installed and enabled in your environment.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe Flash Player to version 18.0.0.252/19.0.0.207 or later (Windows/OS X), 11.2.202.535 or later (Linux), and Adobe AIR to 19.0.0.213 or later. Given Flash's end-of-life status, consider removing Flash entirely as a long-term mitigation.
Flash Player: 18.0.0.252 / 19.0.0.207+ (Win/OS X), 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. Identify the installed Adobe Flash Player or Adobe AIR version by navigating to 'About Flash Player' or checking the application's version information
- 2. For Windows/OS X Flash Player users: Upgrade to version 18.0.0.252 or 19.0.0.207 or later from the Adobe Flash Player download center
- 3. For Linux Flash Player users: Upgrade to version 11.2.202.535 or later
- 4. For Adobe AIR users: Upgrade to version 19.0.0.213 or later
- 5. For Adobe AIR SDK developers: Upgrade to Adobe AIR SDK 19.0.0.213 or later
- 6. For Adobe AIR SDK & Compiler users: Upgrade to version 19.0.0.213 or later
- 7. Verify the upgrade was successful by checking the version number after installation
- 8. Restart any browsers or applications using Flash Player to ensure the new version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2015-7644 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7644 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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