dbcve.org
Adobe AirApplication · Adobe

CVE-2012-4171

MEDIUM · 5.0 CVSS v2.0 Published 2012-08-31
Fix available
A fix is available. Upgrade to after 11.1.115.11 or later.
See remediation →
59/100
Remediation priority · Elevated
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 10.3.183.23 and 11.x before 11.4.402.265 on Windows and Mac OS X, before 10.3.183.23 and 11.x before 11.2.202.238 on Linux, before 11.1.111.16 on Android 2.x and 3.x, and before 11.1.115.17 on Android 4.x; Adobe AIR before 3.4.0.2540; and Adobe AIR SDK before 3.4.0.2540 allow attackers to cause a denial of service (application crash) by leveraging a logic error during handling of Firefox dialogs.

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

A logic error in Adobe Flash Player and AIR causes a denial of service (application crash) when handling Firefox dialogs. The vulnerability affects multiple versions across Windows, Mac OS X, Linux, and Android platforms.

MitigationUpgrade Adobe Flash Player to version 10.3.183.23/11.4.402.265 (Windows/Mac), 11.2.202.238 (Linux), 11.1.111.16 (Android 2.x/3.x), or 11.1.115.17 (Android 4.x); also upgrade Adobe AIR and AIR SDK to 3.4.0.2540 or later.

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 AirApplication
Affected:<= 3.3.0.3670
Adobe Air SdkApplication
Affected:<= 3.3.0.3690
Flash Player For AndroidApplication
Affected:<= 11.1.111.10= 11.1.102.59= 11.1.111.5= 11.1.111.6= 11.1.111.7= 11.1.111.8<= 11.1.115.11= 11.1.112.60= 11.1.112.61= 11.1.115.6
Flash PlayerApplication
Affected:<= 10.3.183.19= 2= 3= 4= 5= 6= 6.0.21.0= 6.0.79= 7.0= 7.0.1= 7.0.14.0= 7.0.19.0

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

AV:N/AC:L/Au:N/C:N/I:N/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
    Windows: Check 'HKLM\SOFTWARE\Macromedia\FlashPlayer' or 'HKLM\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer' in Registry; Mac: Check /Library/Internet Plug-Ins/Flash Player.plugin/Contents/version.plist or run 'defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion'; Linux: Check 'dpkg -l | grep flash' or 'rpm -qa | grep flash'
    Affected if version is 10.3.183.19 or earlier, or matches any of these: 2, 3, 4, 5, 6, 6.0.21.0, 6.0.79, 7.0, 7.0.1, 7.0.14.0, 7.0.19.0, or any 11.1.x version listed in affected Android versions (11.1.111.5-10, 11.1.111.16-115.11, 11.1.112.60-61, 11.1.115.6)
  2. Identify installed Adobe AIR version on desktop
    Windows: Check 'Add or Remove Programs' for Adobe AIR or inspect 'C:\Program Files\Adobe\Adobe AIR\versions.txt'; Mac: Check /Applications/Adobe AIR Installer.app or run 'ls -la /Applications | grep -i air'
    Affected if version is 3.3.0.3670 or earlier
  3. Identify installed Adobe AIR SDK version
    Check for presence of AIR SDK in development environment: inspect SDK readme or version file, typically in the SDK installation root directory (e.g., AIR_SDK_README.txt or similar version metadata file)
    Affected if version is 3.3.0.3690 or earlier
  4. Identify Adobe Flash Player for Android version
    Open Android Settings > Apps > Adobe Flash Player (or Flash Player under Applications), then view the Version information displayed
    Affected if version is 11.1.111.10 or earlier, or matches any of: 11.1.102.59, 11.1.111.5, 11.1.111.6, 11.1.111.7, 11.1.111.8, 11.1.115.11 or earlier, 11.1.112.60, 11.1.112.61, or 11.1.115.6

Your environment is affected if any installed Adobe Flash Player, Adobe AIR, or AIR SDK version matches the affected version ranges listed for this 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 11.1.115.11
Interim mitigation

Upgrade Adobe Flash Player to version 10.3.183.23/11.4.402.265 (Windows/Mac), 11.2.202.238 (Linux), 11.1.111.16 (Android 2.x/3.x), or 11.1.115.17 (Android 4.x); also upgrade Adobe AIR and AIR SDK to 3.4.0.2540 or later.

Fix this in Adobe Air Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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