CVE-2013-1373
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 · uneditedBuffer overflow 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-0642, CVE-2013-0645, CVE-2013-1365, CVE-2013-1366, CVE-2013-1367, CVE-2013-1368, CVE-2013-1369, CVE-2013-1370, and CVE-2013-1372.
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 confidenceBuffer overflow vulnerability in Adobe Flash Player and Adobe AIR affecting Windows, Mac OS X, Linux, and Android. Allows remote attackers to execute arbitrary code via unspecified vectors.
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 regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Flash Player\InstallVersion, or right-click the Flash Player DLL (flash*.ocx) in System32 and view Properties > Details for FileVersionAffected if The installed version falls within: 10.3.x before 10.3.183.63; 11.1.x before 11.1.111.43 or 11.1.115.47; 11.2.x before 11.2.202.270; 11.6.x before 11.6.602.167 or 11.6.602.168
-
Check Adobe Flash Player version on Mac OS XOpen Terminal and run: defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion, or locate the Flash Player.plugin in /Library/Internet Plug-Ins/ and Get Info to view the versionAffected if The installed version falls within the affected ranges listed above for your OS version (Mac-specific versions are 10.3.x before 10.3.183.61 and 11.6.x before 11.6.602.167)
-
Check Adobe Flash Player version on LinuxOpen Terminal and run: rpm -q flash-plugin or dpkg -l | grep flash, or check /usr/lib/flash-plugin/ for the plugin and inspect its version metadataAffected if The installed version is 11.2.x before 11.2.202.270, or falls within other affected ranges for Linux (10.3.x before 10.3.183.61)
-
Check Adobe AIR versionOn Windows, open Add or Remove Programs and look for Adobe AIR, or check the version in C:\Program Files\Adobe\Adobe AIR\versions\<folder>\Adobe AIR.dll. On Mac, check /Applications/Adobe AIR Installer.app or run: ls /Library/Receipts/ | grep AIRAffected if Adobe AIR version is earlier than 3.6.0.597 (Windows/Mac) or the Adobe AIR SDK version is earlier than 3.6.0.599
-
Check if Flash Player browser plugin is presentIn Firefox, go to Add-ons > Plugins and verify Shockwave Flash is listed and enabled. In Chrome, type chrome://plugins and look for Flash. In Internet Explorer, view Manage Add-ons for Shockwave Flash ObjectAffected if A Flash Player plugin version matching the affected version ranges above is installed and enabled in any browser
You are affected if Adobe Flash Player (any browser plugin) or Adobe AIR is installed with a version number lower than the safe thresholds: Flash Player 10.3.183.63+/11.6.602.168+, 11.2.202.270+, 11.1.111.43+/11.1.115.47+; AIR 3.6.0.597+/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 versions 10.3.183.63+/11.6.602.168+ (Windows), 10.3.183.61+/11.6.602.167+ (Mac), 10.3.183.61+/11.2.202.270+ (Linux), 11.1.111.43+ (Android 2.x/3.x), 11.1.115.47+ (Android 4.x); update Adobe AIR to 3.6.0.597+/3.6.0.599+; or uninstall if no longer required.
Flash Player 10.3.183.63/11.2.202.270/11.6.602.168 or later; Adobe AIR 3.6.0.597 or later; Adobe AIR SDK 3.6.0.599 or later
- Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the player or checking the system's program listings
- Identify the currently installed Adobe AIR version via 'Help' > 'About Adobe AIR' or system program listings
- For Flash Player: If version is 10.3.x, upgrade to version 10.3.183.63 or later; if version is 11.2.x, upgrade to version 11.2.202.270 or later; if version is 11.6.x or 11.7.x, upgrade to version 11.6.602.168 or later
- For Adobe AIR: Upgrade to version 3.6.0.597 or later
- For Adobe AIR SDK: Upgrade to version 3.6.0.599 or later
- Download the appropriate fixed version from the official Adobe archives or trusted vendor channels
- Install the updated version and restart any affected browsers or applications
- Verify the installation by checking the updated version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1373 — 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-1373 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