dbcve.org
Flash PlayerApplication · Adobe

CVE-2014-0507

HIGH · 9.3 CVSS v2.0 Published 2014-04-08
Fix available
A fix is available. Upgrade to after 4.0.0.1628 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Buffer overflow in Adobe Flash Player before 11.7.700.275 and 11.8.x through 13.0.x before 13.0.0.182 on Windows and OS X and before 11.2.202.350 on Linux, Adobe AIR before 13.0.0.83 on Android, Adobe AIR SDK before 13.0.0.83, and Adobe AIR SDK & Compiler before 13.0.0.83 allows attackers to execute arbitrary code 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 · high confidence

Buffer overflow vulnerability in Adobe Flash Player and AIR allows attackers to execute arbitrary code via unspecified vectors. The flaw affects multiple versions across Windows, OS X, Linux, and Android platforms.

MitigationUpdate Adobe Flash Player to version 13.0.0.182 (or 11.7.700.275/11.2.202.350 for older branches) and Adobe AIR to version 13.0.0.83, or later patched releases.

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
Flash PlayerApplication
Affected:= 11.0= 11.0.1.152= 11.0.1.153= 11.1= 11.1.102.55= 11.1.102.59= 11.1.102.62= 11.1.102.63= 11.1.111.8= 11.1.111.44= 11.1.111.50= 11.1.111.54
Adobe Air SdkApplication
Affected:<= 4.0.0.1628= 3.0.0.4080= 3.1.0.488= 3.2.0.2070= 3.3.0.3650= 3.3.0.3690= 3.4.0.2540= 3.4.0.2710= 3.5.0.600= 3.5.0.880= 3.5.0.890= 3.5.0.1060
Adobe AirApplication
Affected:<= 4.0.0.1390= 1.0= 1.0.1= 1.0.8.4990= 1.0.4990= 1.1= 1.1.0.5790= 1.5= 1.5.0.7220= 1.5.1= 1.5.1.8210= 1.5.2

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Adobe Flash Player version
    On Windows, check the version in the registry at HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion or view the file properties of NPSWF32.dll in the Flash Player installation folder. On Mac, check /Library/Application Support/Adobe/Flash Player/ and look at the version information for the .app file.
    Affected if The installed version matches any of these: 11.0, 11.0.1.152, 11.0.1.153, 11.1, 11.1.102.55, 11.1.102.59, 11.1.102.62, 11.1.102.63, 11.1.111.8, 11.1.111.44, 11.1.111.50, or 11.1.111.54.
  2. Identify installed Adobe AIR version
    On Windows, open Programs and Features (or Add/Remove Programs) and look for Adobe AIR in the list of installed software. On Mac, check /Applications for Adobe AIR or run 'ls -la /Applications | grep -i air'. The version is typically displayed in the application name or details.
    Affected if The installed version is 4.0.0.1390 or earlier, or matches any of these specific versions: 1.0, 1.0.1, 1.0.8.4990, 1.0.4990, 1.1, 1.1.0.5790, 1.5, 1.5.0.7220, 1.5.1, or 1.5.1.8210.
  3. Identify installed Adobe AIR SDK version
    Check the AIR SDK installation directory for a version file or manifest. On Windows, common paths include C:\Program Files\Adobe\Adobe AIR SDK or within a development IDE. The version may also be visible in the SDK release notes or a version.properties file.
    Affected if The installed SDK version is 4.0.0.1628 or earlier, or matches any of these: 3.0.0.4080, 3.1.0.488, 3.2.0.2070, 3.3.0.3650, 3.3.0.3690, 3.4.0.2540, 3.4.0.2710, 3.5.0.600, 3.5.0.880, 3.5.0.890, or 3.5.0.1060.
  4. Verify if Flash Player is enabled in browser
    If Adobe Flash Player is installed, confirm whether it is enabled in the browser(s) used. In Internet Explorer, check Manage Add-ons. In Chrome, navigate to chrome://plugins. In Firefox, check Add-ons > Plugins. If Flash is disabled, the exploit vector may not be reachable.
    Affected if Adobe Flash Player is installed at an affected version AND is enabled in any web browser.

You are affected if Adobe Flash Player (any of the 12 specific versions listed), Adobe AIR (versions up to 4.0.0.1390 or the 11 specific older versions), or Adobe AIR SDK (versions up to 4.0.0.1628 or the 11 specific older versions) is installed and the relevant component is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 a release after 4.0.0.1628
Interim mitigation

Update Adobe Flash Player to version 13.0.0.182 (or 11.7.700.275/11.2.202.350 for older branches) and Adobe AIR to version 13.0.0.83, or later patched releases.

Recommended fix High confidence

Adobe Flash Player 13.0.0.182 or later (Windows/OS X), 11.2.202.350 or later (Linux); Adobe AIR 13.0.0.83 or later

  1. 1. Identify the currently installed Adobe Flash Player or Adobe AIR version by checking the application's version information
  2. 2. Uninstall the vulnerable version of Adobe Flash Player or Adobe AIR from the system
  3. 3. Download the fixed version from the official Adobe website: for Flash Player 13.0.0.182 or later (Windows/OS X), 11.2.202.350 or later (Linux)
  4. 4. Download Adobe AIR 13.0.0.83 or later from the official Adobe website if using AIR
  5. 5. Install the updated version following the on-screen prompts
  6. 6. Restart any browsers or applications that use Flash Player or AIR
  7. 7. Verify the installed version matches the fixed release to confirm remediation
Caveat Flash Player reached end-of-life on December 31, 2020; consider migrating away from Flash-based content as modern browsers have deprecated or removed Flash support

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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