CVE-2013-0637
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.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 allow attackers to obtain sensitive information 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 · moderate confidenceAdobe Flash Player and Adobe AIR contain an information disclosure vulnerability that allows attackers to obtain sensitive information via unspecified vectors. The vulnerability affects multiple platforms including Windows, Mac OS X, Linux, and Android across various older versions of the software.
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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Windows Control Panel, select 'Programs and Features', find 'Adobe Flash Player XX' in the list, or open Internet Explorer, go to Manage Add-ons, and view the Flash Player plugin version. Alternatively, visit Adobe's version check page at https://www.adobe.com/software/flash/about/ in each installed browser.Affected if The installed version is 10.3.x before 10.3.183.63, 11.6.x before 11.6.602.168, 11.2.x before 11.2.202.270, 11.1.x before 11.1.111.43 (Android 2.x/3.x), or 11.1.x before 11.1.115.47 (Android 4.x)
-
Check Adobe Flash Player version on Mac OS XOpen Finder, go to /Library/Internet Plug-Ins/ and locate 'Flash Player.plugin' or 'PepperFlashPlayer.plugin' (Chrome. Right-click on the .plugin file, select 'Get Info' to view the version number.Affected if The installed version matches any of the affected version ranges listed for Flash Player
-
Check Adobe Flash Player version on LinuxOpen a terminal and run: rpm -q flash-player-plugin (for RPM-based distributions) or dpkg -l | grep flash (for Debian-based). Alternatively, open a browser and visit Adobe's version check page.Affected if The installed version is 11.2.x before 11.2.202.270
-
Check Adobe AIR versionOn Windows, open Control Panel, select 'Programs and Features', and look for 'Adobe AIR' in the installed programs list. On Mac, open /Applications and locate Adobe AIR, then right-click and select 'Get Info'. Run 'adobeair -version' in command line if available.Affected if The installed Adobe AIR version is lower than 3.6.0.597
-
Check Adobe AIR SDK versionIf you have Adobe AIR SDK installed for development, check the version by looking in the SDK installation directory. Navigate to the AIR SDK folder and locate a version file or check the 'readme.txt' or 'VERSION' file included with the SDK.Affected if The installed Adobe AIR SDK version is lower than 3.6.0.599
Your environment is affected if any installed Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version falls within the affected ranges specified for CVE-2013-0637.
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.
From vendor data3.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+ (Android 2.x/3.x)/11.1.115.47+ (Android 4.x). Update Adobe AIR to 3.6.0.597+ and Adobe AIR SDK to 3.6.0.599+.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0637 — 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-0637 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