dbcve.org
Flash PlayerApplication · Adobe

CVE-2013-5332

HIGH · 9.3 CVSS v2.0 Published 2013-12-11
Fix available
A fix is available. Upgrade to 3.9.0.1380 / 11.2.202.332 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 11.7.700.257 and 11.8.x and 11.9.x before 11.9.900.170 on Windows and Mac OS X and before 11.2.202.332 on Linux, Adobe AIR before 3.9.0.1380, Adobe AIR SDK before 3.9.0.1380, and Adobe AIR SDK & Compiler before 3.9.0.1380 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.

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
How this class of weakness works · CWE-94

The application evaluates attacker-influenced input as code, handing them a way to run logic inside the process. Depending on the runtime this can escalate directly to remote code execution. Remediation means removing dynamic evaluation of untrusted input and replacing it with safe, data-driven alternatives.

General guidance for the code injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.0, < 11.7.700.257>= 11.8, < 11.8.800.175>= 11.9, < 11.9.900.700>= 11.0, < 11.2.202.332
AirApplication
Affected:< 3.9.0.1380
Air SdkApplication
Affected:< 3.9.0.1380

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 3.9.0.1380 / 11.2.202.332 / 11.7.700.257 or later
Fixed in 3.9.0.138011.2.202.33211.7.700.257
Vendor patch helpx.adobe.com →
Recommended fix High confidence

Flash Player 11.7.700.257 (or 11.8.800.175/11.9.900.700/11.2.202.332 for respective branches); AIR 3.9.0.1380; AIR SDK 3.9.0.1380

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click context menu or visiting 'about:flash' in the browser
  2. 2. Identify the currently installed Adobe AIR version from Add/Remove Programs (Windows) or the AIR Application Installer (Mac/Linux)
  3. 3. For Flash Player: Navigate to https://get.adobe.com/flashplayer/ and download version 11.7.700.257 or later (or 11.2.202.332 or later for Linux)
  4. 4. For Adobe AIR: Navigate to https://get.adobe.com/air/ and download version 3.9.0.1380 or later
  5. 5. For Adobe AIR SDK: Download version 3.9.0.1380 or later from https://airsdk.harman.com/ or Adobe's archive
  6. 6. Close all browser instances and applications using Flash Player before installation
  7. 7. Run the installer with administrator privileges and follow the on-screen prompts
  8. 8. Restart the browser and verify the updated version in 'About Flash Player'
Caveat Upgrading Flash Player and AIR may cause incompatibility with older content relying on deprecated features; some browser integrations may require re-enabling after upgrade

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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