CVE-2013-1380
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 10.3.183.75 and 11.x before 11.7.700.169 on Windows and Mac OS X, before 10.3.183.75 and 11.x before 11.2.202.280 on Linux, before 11.1.111.50 on Android 2.x and 3.x, and before 11.1.115.54 on Android 4.x; Adobe AIR before 3.7.0.1530; and Adobe AIR SDK & Compiler before 3.7.0.1530 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2013-1378.
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 analysisA detailed technical summary for this CVE is being prepared.
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<= 10.3.183.68= 6.0.21.0= 6.0.79= 7.0= 7.0.1= 7.0.14.0= 7.0.19.0= 7.0.24.0= 7.0.25= 7.0.53.0= 7.0.60.0= 7.0.61.0<= 3.6.0.6090= 3.6.0.597<= 3.6.0.6090= 3.6.0.599CVSS 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
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 · scopedFlash Player 10.3.183.75+/11.7.700.169+ (Win/Mac), 11.2.202.280+ (Linux), 11.1.111.50+ (Android 2.x/3.x), 11.1.115.54+ (Android 4.x); Adobe AIR 3.7.0.1530+; Adobe AIR SDK 3.7.0.1530+
- Identify the currently installed Adobe Flash Player version and platform (Windows, Mac OS X, Linux, or Android)
- Identify the currently installed Adobe AIR or AIR SDK version
- For Flash Player on Windows/Mac OS X: upgrade to version 10.3.183.75 or later, or 11.7.700.169 or later
- For Flash Player on Linux: upgrade to version 10.3.183.75 or later, or 11.2.202.280 or later
- For Flash Player on Android 2.x/3.x: upgrade to version 11.1.111.50 or later
- For Flash Player on Android 4.x: upgrade to version 11.1.115.54 or later
- For Adobe AIR: upgrade to version 3.7.0.1530 or later
- For Adobe AIR SDK/Compiler: upgrade to version 3.7.0.1530 or later
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1380 — 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-2013-1380 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