Flash PlayerApplication · Adobe

CVE-2015-5547

HIGH · 10.0 CVSS v2.0 Published 2015-08-14

Fix available

A fix is available. Upgrade to after 18.0.0.209 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click Patch available

Official description

NVD · unedited

Adobe Flash Player before 18.0.0.232 on Windows and OS X and before 11.2.202.508 on Linux, Adobe AIR before 18.0.0.199, Adobe AIR SDK before 18.0.0.199, and Adobe AIR SDK & Compiler before 18.0.0.199 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-5544, CVE-2015-5545, CVE-2015-5546, CVE-2015-5548, CVE-2015-5549, CVE-2015-5552, and CVE-2015-5553.

Technical summary

dbcve analysis · high confidence

Memory corruption vulnerability in Adobe Flash Player and AIR allowing arbitrary code execution or denial of service. The flaw exists in unspecified vectors within the Flash Player and AIR runtime components prior to version 18.0.0.232 (Windows/OS X), 11.2.202.508 (Linux), and AIR 18.0.0.199.

MitigationUpdate Adobe Flash Player to version 18.0.0.232 or later (Windows/OS X) / 11.2.202.508 or later (Linux), and Adobe AIR/AIR SDK to version 18.0.0.199 or later. Consider removing Flash if no longer required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Flash PlayerApplication

Affected:<= 11.2.202.491<= 18.0.0.209

AirApplication

Affected:<= 18.0.0.180

Air SdkApplication

Affected:<= 18.0.0.180

Air Sdk \& CompilerApplication

Affected:<= 18.0.0.180

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Adobe Flash Player version in browsers

Open each installed browser and navigate to 'About Flash Player' or use 'Adobe Flash Player Check' at adobe.com. Alternatively, on Windows check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\Version (32-bit) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer\Version (64-bit), and on Linux check /usr/lib/flash-plugin/libflashplayer.so properties or rpm -q flash-plugin

Affected if The installed version is 11.2.202.491 or earlier, or 18.0.0.209 or earlier (but newer than 11.2.202.491)
Check Adobe AIR desktop runtime version

On Windows, go to Control Panel > Programs and Features and look for 'Adobe AIR' to see the installed version, or check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR\Version. On macOS, check /Applications/Adobe AIR Installer.app or run 'defaults read /Applications/Adobe\ AIR\ Installer.app/Contents/Info CFBundleVersion'. On Linux, check /opt/adobe-air-sdk/adrfloordata or run 'adobe-air --version' if available.

Affected if The installed version is 18.0.0.180 or earlier
Check Adobe AIR SDK version

On Windows, check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR SDK\Version or look for the SDK installation directory (commonly C:\Program Files\Adobe\AIR SDK or C:\Users\User\AppData\Local\Adobe\AIR). On macOS, check /Applications/Adobe Flash Builder 4.7/eclipse/plugins or look for AIR SDK in the Adobe Flash Builder installation. On Linux, check /opt/air-sdk or the user's flash-builder directory. Look for a version file or 'AIR SDK Read Me.txt' that contains the version number.

Affected if The installed AIR SDK version is 18.0.0.180 or earlier
Check if Flash Player plugin exists in web browsers

For Internet Explorer, check C:\Windows\System32\Macromed\Flash for the Flash.ocx file and right-click > Properties to view version. For Chrome, navigate to chrome://components/ and find Flash Player. For Firefox, navigate to about:addons > Plugins and look for 'Shockwave Flash'. For Edge, check C:\Users\User\AppData\Local\Microsoft\Edge\User Data\WidevinePlugins or the system Flash directory.

Affected if Any installed Flash Player plugin version matches the affected version ranges from steps 1-3

The environment is affected if Adobe Flash Player version is 11.2.202.491 or earlier, or between 11.2.202.492 and 18.0.0.209 inclusive, or if Adobe AIR/AIR SDK version is 18.0.0.180 or earlier.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 18.0.0.209

Vendor patch helpx.adobe.com →

Interim mitigation

Update Adobe Flash Player to version 18.0.0.232 or later (Windows/OS X) / 11.2.202.508 or later (Linux), and Adobe AIR/AIR SDK to version 18.0.0.199 or later. Consider removing Flash if no longer required.

Recommended fix High confidence

Flash Player 18.0.0.232 (Windows/OS X) or 11.2.202.508 (Linux); Adobe AIR 18.0.0.199; Adobe AIR SDK 18.0.0.199; Adobe AIR SDK & Compiler 18.0.0.199

1. Identify which Adobe product is installed (Flash Player, Adobe AIR, AIR SDK, or AIR SDK & Compiler)
2. Check the current installed version of the product
3. For Flash Player: Download version 18.0.0.232 (Windows/OS X) or 11.2.202.508 (Linux) from the Adobe Security Bulletin APSB15-19
4. For Adobe AIR: Download version 18.0.0.199 from the Adobe Security Bulletin APSB15-19
5. For Adobe AIR SDK: Download version 18.0.0.199 from the Adobe Security Bulletin APSB15-19
6. For Adobe AIR SDK & Compiler: Download version 18.0.0.199 from the Adobe Security Bulletin APSB15-19
7. Uninstall the existing version
8. Install the appropriate fixed version

Caveat Flash Player reached end of life in December 2020; ensure browser compatibility and consider migrating away from Flash-based content

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
Implementation2.0 h
Testing1.0 h
Review / QA1.0 h

5.0 hours of engineering $890

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,424.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-5547 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-5547?

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.

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

At a glance

A fix existsUpgrade to after 18.0.0.209 or later

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 38.2%

Affects: Flash Player

Remediation

A high-priority fix

Fix this in Flash Player 5 hrs · Low

Typical engagement from $890

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2015-5547 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References