dbcve.org
AirApplication · Adobe

CVE-2015-7633

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-7627, CVE-2015-7630, 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 AIR allowing remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. Affects Windows, OS X, and Linux platforms.

MitigationUpdate Adobe Flash Player to version 18.0.0.252 or later (Windows/OS X) or 11.2.202.535 or later (Linux), and Adobe AIR to 19.0.0.213 or later. Consider migrating away from Flash given its end-of-life status.

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:<= 11.2.202.521<= 19.0.0.185

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. Identify installed Adobe Flash Player version
    Open a web browser and navigate to 'about:flash' (Chrome) or check the Flash Player version via the Adobe website's version check page, or on Windows check the Flash.ocx file properties in the System32 folder
    Affected if The displayed version is 11.2.202.521 or earlier, or 19.0.0.185 or earlier (for the 19.x branch)
  2. Identify installed Adobe AIR version
    On Windows, open 'Add or Remove Programs' and locate Adobe AIR, or check the AIR runtime version via the AIR Application Installer. On OS X, check /Applications/Adobe AIR Installer.app or the AIR version in System Preferences if available
    Affected if The installed version is 19.0.0.190 or earlier
  3. Check for Adobe AIR SDK or Adobe AIR SDK & Compiler installations
    If you are a developer using the Adobe AIR SDK, locate the SDK installation directory and check the 'version' file or the AIR SDK release notes included in the SDK package
    Affected if The SDK version is 19.0.0.190 or earlier
  4. Verify platform is affected
    Confirm the operating system is Windows, OS X, or Linux (as listed in the affected platforms for this CVE)
    Affected if The system runs Windows, OS X, or Linux with the vulnerable Adobe product installed
  5. Compare installed version against affected ranges
    Document the exact version number found and compare it against the known vulnerable versions: Flash Player <= 11.2.202.521, Flash Player <= 19.0.0.185, Adobe AIR <= 19.0.0.190
    Affected if The installed version falls within or below any of these thresholds

You are affected if Adobe Flash Player version 11.2.202.521 or earlier (or 19.0.0.185 or earlier for the 19.x line) or Adobe AIR/SDK version 19.0.0.190 or earlier is installed on a Windows, OS X, or Linux system.

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 (Windows/OS X) or 11.2.202.535 or later (Linux), and Adobe AIR to 19.0.0.213 or later. Consider migrating away from Flash given its end-of-life status.

Recommended fix High confidence

Adobe Flash Player 19.0.0.207 (Windows/OS X) or 11.2.202.535 (Linux); Adobe AIR 19.0.0.213; Adobe AIR SDK 19.0.0.213

  1. Identify which Adobe product is installed: Flash Player, Adobe AIR, or Adobe AIR SDK/Compiler. Check the current version in the system's program information.
  2. Navigate to the Adobe security bulletin APSB15-25 at https://helpx.adobe.com/security/products/flash-player/apsb15-25.html to obtain the official patched installer for your product.
  3. For Flash Player: Download the fixed version 19.0.0.207 (Windows/OS X) or 11.2.202.535 (Linux), or version 18.0.0.252 if downgrading from 19.x.
  4. For Adobe AIR: Download version 19.0.0.213.
  5. For Adobe AIR SDK or AIR SDK & Compiler: Download version 19.0.0.213.
  6. Run the installer with appropriate system privileges and complete the installation.
  7. Restart any browsers or applications that use Flash Player or AIR after installation.
  8. Verify the installed version matches the fixed release to confirm remediation was successful.
Caveat This upgrade may break compatibility with older applications that depend on deprecated Flash or AIR features; ensure legacy application testing before deployment 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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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