CVE-2013-1374
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 · uneditedUse-after-free vulnerability in Adobe Flash Player before 10.3.183.63 and 11.x before 11.6.602.168 on Windows, before 10.3.183.61 and 11.x before 11.6.602.167 on Mac OS X, before 10.3.183.61 and 11.x before 11.2.202.270 on Linux, before 11.1.111.43 on Android 2.x and 3.x, and before 11.1.115.47 on Android 4.x; Adobe AIR before 3.6.0.597; and Adobe AIR SDK before 3.6.0.599 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2013-0644 and CVE-2013-0649.
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 confidenceUse-after-free vulnerability in Adobe Flash Player and Adobe AIR that allows attackers to execute arbitrary code via unspecified vectors. The flaw occurs due to improper memory management where memory is accessed after being freed, enabling code execution in the context of the current user.
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>= 10.3, < 10.3.183.63>= 11.6, < 11.6.602.168>= 10.3, < 10.3.183.61>= 11.2, < 11.2.202.270>= 11.1, < 11.1.111.43>= 11.1, < 11.1.115.47>= 11.6, < 11.6.602.167< 3.6.0.597< 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
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 checksWork through these to decide whether this CVE applies to you.
-
Check Adobe Flash Player version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or check the file properties of the Flash Player plugin (flash*.ocx in System32 or NPSWF32.dll in browser plugin folders).Affected if The version string is lower than 10.3.183.63, 11.6.602.168, 11.2.202.270, 11.1.111.43, or 11.1.115.47 depending on the major version branch.
-
Check Adobe Flash Player version on MacLocate /Library/Application Support/Adobe/Flash Player/ and inspect the version file, or within Safari go to Help > About Plug-ins to see the Flash Player version.Affected if The displayed version is below the fixed versions for the respective major release branch.
-
Check Adobe Flash Player version in browsers (cross-platform)Visit a site that displays Flash Player version information, or in Chrome navigate to chrome://plugins and locate the Flash entry to view its version.Affected if The reported version falls within the affected ranges listed for this CVE.
-
Check Adobe AIR runtime version on WindowsOpen Programs and Features (or Add/Remove Programs), locate Adobe AIR in the list, and observe the version column.Affected if The installed version is lower than 3.6.0.597.
-
Check Adobe AIR SDK versionIf the AIR SDK is installed locally, check the version file in the SDK root directory (often named VERSION or visible in the SDK Manager), or run 'adl -version' from the SDK bin folder.Affected if The SDK version is below 3.6.0.599.
A system is affected if Adobe Flash Player is any version below 10.3.183.63/11.6.602.168/11.2.202.270/11.1.111.43/11.1.115.47 (depending on branch), or Adobe AIR is below 3.6.0.597, or the AIR SDK is below 3.6.0.599.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.6.0.5973.6.0.59910.3.183.61
Update Adobe Flash Player to version 10.3.183.63+/11.6.602.168+ (Windows), 11.6.602.167+ (Mac), 11.2.202.270+ (Linux), or 11.1.111.43+/11.1.115.47+ (Android); update Adobe AIR to 3.6.0.597+ and AIR SDK to 3.6.0.599+. Consider disabling Flash in browsers if updates cannot be applied.
Flash Player: 10.3.183.63/10.3.183.61/11.6.602.168/11.2.202.270/11.1.111.43/11.1.115.47 (platform-dependent); AIR: 3.6.0.597; AIR SDK: 3.6.0.599
- 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' or visiting the version check page at adobe.com/software/flash/about/
- 2. Identify whether Adobe AIR is installed by checking the AIR version in system settings or control panel
- 3. For Windows: Download Flash Player 10.3.183.63 (for 10.3.x branch) or 11.6.602.168 (for 11.x branch) from the official Adobe bulletin (www.adobe.com/support/security/bulletins/apsb13-09.html)
- 4. For Mac OS X: Download Flash Player 10.3.183.61 from the official Adobe bulletin
- 5. For Linux: Download Flash Player 10.3.183.61 or 11.2.202.270 depending on version branch from the official Adobe bulletin
- 6. For Android: Download Flash Player 11.1.111.43 (for Android 2.x/3.x) or 11.1.115.47 (for Android 4.x) from Google Play Store or Adobe
- 7. If using Adobe AIR, upgrade to version 3.6.0.597
- 8. If using Adobe AIR SDK, upgrade to version 3.6.0.599
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1374 — 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-1374 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