dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-7627

HIGH · 10.0 CVSS v2.0 Published 2015-10-15
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
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 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-7625, CVE-2015-7626, 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 confidence

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution or denial of service. Affects specific versions across Windows, OS X, and Linux platforms. This is one of multiple critical Flash vulnerabilities patched in the September 2015 security update.

MitigationUpdate Adobe Flash Player to version 18.0.0.252/19.0.0.207 (Windows/OS X) or 11.2.202.535 (Linux), and Adobe AIR to 19.0.0.213 or later. Consider removing Flash entirely if unnecessary, as it reached end-of-life in December 2020.

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
Flash PlayerApplication
Affected:<= 11.2.202.521<= 19.0.0.185
AirApplication
Affected:<= 19.0.0.190
Air SdkApplication
Affected:<= 19.0.0.190
Air Sdk \& CompilerApplication
Affected:<= 19.0.0.190

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 Registry Editor and navigate to HKLM\SOFTWARE\Macromedia\FlashPlayer\Version (or HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion for 64-bit). Alternatively, locate NPSWF32.dll in the browser plugins folder and view its file properties.
    Affected if The reported version is 11.2.202.521 or earlier, or 19.0.0.185 or earlier.
  2. Check Adobe Flash Player on macOS or Linux
    On macOS, inspect /Library/Internet Plug-Ins/Flash Player.plugin/Contents/Info.plist for CFBundleVersion. On Linux, check the package manager (dpkg -l | grep flash) or locate libflashplayer.so and view its properties.
    Affected if The reported version is 11.2.202.521 or earlier, or 19.0.0.185 or earlier.
  3. Check Adobe AIR runtime version on Windows
    Open Programs and Features (or Add/Remove Programs) and look for Adobe AIR entry, or check the version in the installation directory typically under C:\Program Files\Adobe\Adobe AIR\versions\AIR\. You can also view the version via the file properties of the Adobe AIR executable.
    Affected if The installed version is 19.0.0.190 or earlier.
  4. Check Adobe AIR SDK or AIR SDK & Compiler version
    If installed as a standalone SDK, locate the SDK directory (commonly under C:\Program Files\Adobe\Adobe Flash Builder\sdks\ or a custom path) and check the version file or AIR SDK version text file included in the SDK folder.
    Affected if The SDK version is 19.0.0.190 or earlier.

If any installed Adobe Flash Player, Adobe AIR runtime, or Adobe AIR SDK version falls within the affected ranges listed (Flash Player <= 11.2.202.521 or <= 19.0.0.185; AIR <= 19.0.0.190), the environment is vulnerable to CVE-2015-7627.

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 (Windows/OS X) or 11.2.202.535 (Linux), and Adobe AIR to 19.0.0.213 or later. Consider removing Flash entirely if unnecessary, as it reached end-of-life in December 2020.

Recommended fix High confidence

Flash Player: 18.0.0.252/19.0.0.207 (Windows/OS X), 11.2.202.535 (Linux) | AIR/AIR SDK/AIR SDK & Compiler: 19.0.0.213

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the player or checking the system plugin list.
  2. 2. Identify the currently installed Adobe AIR/AIR SDK/AIR SDK & Compiler version in the system or development environment.
  3. 3. For Flash Player on Windows or OS X: Upgrade to version 18.0.0.252 or 19.0.0.207 or later.
  4. 4. For Flash Player on Linux: Upgrade to version 11.2.202.535 or later.
  5. 5. For Adobe AIR: Upgrade to version 19.0.0.213 or later.
  6. 6. For Adobe AIR SDK: Upgrade to version 19.0.0.213 or later.
  7. 7. For Adobe AIR SDK & Compiler: Upgrade to version 19.0.0.213 or later.
  8. 8. Restart any browsers or applications using Flash Player or AIR after the update.
Caveat Note: Adobe Flash Player and AIR are deprecated technologies. Ensure any dependent applications are compatible with the newer versions before upgrading in production environments.

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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