CVE-2015-7625
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 · uneditedAdobe 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 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-7626, CVE-2015-7627, CVE-2015-7630, CVE-2015-7633, and CVE-2015-7634.
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 confidenceMemory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. CVSS 10 indicates critical severity with potential for complete system compromise.
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.185<= 11.2.202.521<= 19.0.0.190<= 19.0.0.190<= 19.0.0.190CVSS 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 Flash Player version in WindowsOpen command prompt and run: reg query 'HKLM\SOFTWARE\Macromedia\FlashPlayer' /v Version (for system-wide) or check browser add-on version in Internet Explorer via Manage Add-ons, or Chrome via chrome://componentsAffected if Version is 19.0.0.185 or lower, or 11.2.202.521 or lower on Linux-based systems
-
Check Flash Player version on LinuxRun: dpkg -l | grep flash or rpm -q flash-plugin or check /usr/lib/flash-plugin/ for version fileAffected if Version is 11.2.202.521 or lower
-
Check Adobe AIR versionOpen Control Panel > Programs and Features, or run: reg query 'HKLM\SOFTWARE\Adobe\AIR' /v Version on Windows; on Mac check /Applications/Adobe AIR Installer.app contentsAffected if Version is 19.0.0.190 or lower
-
Check Adobe AIR SDK versionLocate AIR SDK installation directory and check version.properties or air-sdk-version file, or run: adt -version if AIR SDK is installedAffected if Version is 19.0.0.190 or lower
-
Verify Flash Player is enabled in browsersCheck browser settings: Internet Explorer > Manage Add-ons > Shockwave Flash Object; Chrome > chrome://plugins; Firefox > Add-ons > PluginsAffected if Flash Player plugin is enabled AND version is within affected range from step 1 or 2
Your environment is affected if any installed Adobe Flash Player version is 19.0.0.185 or lower (or 11.2.202.521 or lower on Linux) OR any Adobe AIR/AIR SDK version is 19.0.0.190 or lower, with the vulnerable component enabled in the browser or as an installed application.
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 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. If immediate patching is not feasible, consider disabling Flash Player in browsers or removing it entirely given its end-of-life status.
Flash Player: 18.0.0.252/19.0.0.207/11.2.202.535 (depending on branch); AIR: 19.0.0.213; AIR SDK: 19.0.0.213
- Identify the exact Adobe Flash Player or AIR version currently installed
- For Flash Player 18.x: upgrade to version 18.0.0.252 or later
- For Flash Player 19.x: upgrade to version 19.0.0.207 or later
- For Flash Player 11.x on Linux: upgrade to version 11.2.202.535 or later
- For Adobe AIR: upgrade to version 19.0.0.213 or later
- For Adobe AIR SDK: upgrade to version 19.0.0.213 or later
- For Adobe AIR SDK & Compiler: upgrade to version 19.0.0.213 or later
- Verify the installed version matches or exceeds the fixed version after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7625 — 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-7625 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