Adobe Air SdkApplication · Adobe

CVE-2014-0537

HIGH · 7.5 CVSS v2.0 Published 2014-07-09
Fix available
A fix is available. Upgrade to after 14.0.0.110 or later.
See remediation →
84/100
Remediation priority · High
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
Adobe Flash Player before 13.0.0.231 and 14.x before 14.0.0.145 on Windows and OS X and before 11.2.202.394 on Linux, Adobe AIR before 14.0.0.137 on Android, Adobe AIR SDK before 14.0.0.137, and Adobe AIR SDK & Compiler before 14.0.0.137 allow attackers to bypass intended access restrictions via unspecified vectors, a different vulnerability than CVE-2014-0539.

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 confidence

Adobe Flash Player and Adobe AIR contain a security vulnerability that allows attackers to bypass intended access restrictions. The flaw affects multiple versions across Windows, OS X, Linux, and Android platforms. This is a distinct vulnerability from CVE-2014-0539.

MitigationUpdate Adobe Flash Player to version 13.0.0.231 or later (14.x to 14.0.0.145 or later on Windows/OS X, 11.2.202.394 or later on Linux), and Adobe AIR to 14.0.0.137 or later. Organizations should also consider removing deprecated Flash Player installations where possible.

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
Adobe Air SdkApplication
Affected:<= 14.0.0.110= 13.0.0.83= 13.0.0.111
Flash PlayerApplication
Affected:<= 13.0.0.223= 13.0.0.182= 13.0.0.201= 13.0.0.206= 13.0.0.214= 14.0.0.125<= 11.2.202.378= 11.2.202.223= 11.2.202.228= 11.2.202.233= 11.2.202.235= 11.2.202.236
Adobe AirApplication
Affected:<= 14.0.0.110= 13.0.0.83= 13.0.0.111

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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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
    Check the Flash Player version in your browser (navigate to 'about:plugin' in Firefox or chrome://plugins in Chrome) or check the file version of 'Flash32.ocx' or 'Flash64.ocx' in %WINDIR%\System32\Macromed\Flash\ on Windows, or /Library/Application Support/Adobe/Flash Player/ on macOS, or /usr/lib/flash-plugin/ on Linux
    Affected if The installed version is 11.2.202.378 or lower, or is one of 11.2.202.223, 11.2.202.228, 11.2.202.233, 11.2.202.235, 11.2.202.236, 13.0.0.182, 13.0.0.201, 13.0.0.206, 13.0.0.214, 13.0.0.223, or 14.0.0.125
  2. Identify installed Adobe AIR version
    Check the version through the Adobe AIR Settings Manager at 'https://airsdk.harman.com/' or look for the AIR runtime in Program Files on Windows (/Applications on macOS) and inspect the version info of the AIR application
    Affected if The installed version is 14.0.0.110 or lower, or is exactly 13.0.0.83 or 13.0.0.111
  3. Identify installed Adobe AIR SDK version
    Check the version of the AIR SDK by reviewing the 'version.properties' file within the SDK installation directory or running 'adl -version' if the SDK tools are in your PATH
    Affected if The SDK version is 14.0.0.110 or lower, or is exactly 13.0.0.83 or 13.0.0.111

You are affected if any installed Adobe Flash Player, Adobe AIR runtime, or Adobe AIR SDK version matches one of the specific versions or falls within the vulnerable version ranges listed in the CVE.

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.

From vendor data
Upgrade available Upgrade to a release after 14.0.0.110
Interim mitigation

Update Adobe Flash Player to version 13.0.0.231 or later (14.x to 14.0.0.145 or later on Windows/OS X, 11.2.202.394 or later on Linux), and Adobe AIR to 14.0.0.137 or later. Organizations should also consider removing deprecated Flash Player installations where possible.

Fix this in Adobe Air Sdk Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0537 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