dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022.
Enterprise Linux DesktopOperating system · Redhat

CVE-2012-1535

HIGH · 7.8 CVSS v3.1 Published 2012-08-15
Fix available
A fix is available. Upgrade to 11.2.202.238 / 11.3.300.271 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild High EPSS No privileges Patch available

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
Unspecified vulnerability in Adobe Flash Player before 11.3.300.271 on Windows and Mac OS X and before 11.2.202.238 on Linux allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via crafted SWF content, as exploited in the wild in August 2012 with SWF content in a Word document.

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

Unspecified vulnerability in Adobe Flash Player allows remote attackers to execute arbitrary code or cause denial of service via crafted SWF content. Exploited in the wild in August 2012 through SWF embedded in Word documents.

MitigationUpdate Adobe Flash Player to version 11.3.300.271 or later for Windows/Mac OS X, or 11.2.202.238 or later for Linux.

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
Enterprise Linux DesktopOperating system
Affected:= 5.0
Enterprise Linux ServerOperating system
Affected:= 5.0
Enterprise Linux WorkstationOperating system
Affected:= 5.0
Flash PlayerApplication
Affected:< 11.3.300.271< 11.2.202.238
OpensuseOperating system
Affected:= 11.4= 12.1
Linux Enterprise DesktopOperating system
Affected:= 10

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Confirm Adobe Flash Player is installed
    Check for Flash Player plugin in browsers (about:plugins in Firefox, chrome://plugins in Chrome) or look for npapi or pepflash DLL files in browser plugin directories (e.g., /usr/lib/flash-plugin, C:\Windows\System32\Macromed\Flash)
    Affected if Adobe Flash Player is present on the system
  2. Identify the installed Flash Player version
    In Firefox, navigate to about:plugins and locate the Shockwave Flash entry; in Chrome, go to chrome://components; on Linux, check /usr/lib/flash-plugin or run rpm -q flash-plugin; on Windows, check registry key HKLM\SOFTWARE\Macromedia\FlashPlayer or inspect the Flash DLL file properties
    Affected if Version is below 11.3.300.271 (Windows/Mac) or below 11.2.202.238 (Linux)
  3. Determine the operating system platform
    Run 'uname -a' on Linux or check System Properties on Windows; identify if the system is RHEL 5.0, openSUSE 11.4/12.1, SUSE Linux Enterprise Desktop 10, or a Windows/Mac OS X host
    Affected if Running RHEL 5.0, openSUSE 11.4, openSUSE 12.1, or SUSE Linux Enterprise Desktop 10 with any Flash version installed
  4. Check if Flash is actively enabled in web browsers
    Inspect browser settings or plugin manager to see if the Flash plugin is set to 'Always Activate' or 'Enabled' for all websites; test by loading a Flash-enabled page
    Affected if Flash Player plugin is enabled in any web browser used to open untrusted documents or browse the web
  5. Inspect recently opened document files
    Check recent Microsoft Word documents, email attachments, or downloaded files for embedded SWF objects; examine file contents using tools like 'strings' or hex editors to look for 'CWS' or 'FWS' SWF magic bytes
    Affected if User has opened Word documents or other files originating from untrusted sources that may contain embedded malicious Flash content

A user is affected if Adobe Flash Player is installed with a version below 11.3.300.271 (Windows/Mac) or below 11.2.202.238 (Linux), or if the system runs the specific Red Hat/openSUSE/SUSE distributions listed, and the Flash plugin is enabled in browsers or used to open untrusted documents.

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 11.2.202.238 / 11.3.300.271 or later
Fixed in 11.2.202.23811.3.300.271
Vendor patch www.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 11.3.300.271 or later for Windows/Mac OS X, or 11.2.202.238 or later for Linux.

Recommended fix High confidence

Adobe Flash Player 11.2.202.238 (Linux) or 11.3.300.271 (Windows/Mac) or later

  1. Identify the installed Flash Player version by navigating to 'About Flash Player' in the browser or checking the plugin directly
  2. For Linux systems: upgrade to Adobe Flash Player 11.2.202.238 or later
  3. For Windows/Mac OS X systems: upgrade to Adobe Flash Player 11.3.300.271 or later
  4. On Red Hat Enterprise Linux 5 systems: install the flash-plugin package from RHN or the Red Hat Network
  5. On openSUSE 11.4 and 12.1: install available security updates for the flash-player package
  6. Alternatively, disable the Flash Player browser plugin in all browsers as a mitigation
  7. Consider migrating away from Flash Player as it reached end-of-life in December 2020
Caveat Flash Player is deprecated and reached end-of-life in December 2020; consider migrating to HTML5-based alternatives

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

Fix this in Enterprise Linux Desktop Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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