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-2017-11292

HIGH · 8.8 CVSS v3.1 Published 2017-10-22
Fix available
A fix is available. Upgrade to after 27.0.0.159 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable 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
Adobe Flash Player version 27.0.0.159 and earlier has a flawed bytecode verification procedure, which allows for an untrusted value to be used in the calculation of an array index. This can lead to type confusion, and successful exploitation could lead to arbitrary code execution.

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

Adobe Flash Player contains a flawed bytecode verification procedure that allows untrusted values to be used in array index calculations, leading to type confusion. Successful exploitation enables arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Flash Player to a version later than 27.0.0.159, or preferably remove Flash Player entirely given its end-of-life status and replace with modern web technologies.

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:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
Flash Player Desktop RuntimeApplication
Affected:<= 27.0.0.159
Flash PlayerApplication
Affected:<= 27.0.0.130<= 27.0.0.159

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

CVSS:3.1/AV:N/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 the presence of Flash Player files: On Windows, look in C:\Windows\System32\Macromed\Flash or browser plugin directories; On Linux, check /usr/lib/flash-plugin or ~/.mozilla/plugins; On macOS, check /Library/Internet Plug-Ins
    Affected if Adobe Flash Player is found installed on the system
  2. Identify the installed Flash Player version
    Windows: Right-click npflash.dll or Flash32_xx_x_x_xxx.ocx and select Properties > Details to view the File Version; Linux: Run rpm -q flash-plugin or dpkg -l | grep flash; macOS: Right-click Flash Player in /Library/Internet Plug-Ins and select Get Info to see the version
    Affected if The installed version cannot be determined or the file is not found
  3. Compare the version against affected ranges
    Compare the identified version number to the affected ranges: Adobe Flash Player Desktop Runtime versions <= 27.0.0.159 and Adobe Flash Player versions <= 27.0.0.130 or <= 27.0.0.159 are vulnerable
    Affected if The installed version is 27.0.0.159 or earlier, or 27.0.0.130 or earlier (depending on the specific product line)
  4. Check for Flash Player in web browsers
    Open each installed browser and navigate to adobe.com/go/aboutflashplayer to view the installed version, or visit a version detection page like about:plugins (Firefox) or chrome://plugins (Chrome)
    Affected if Browser plugins show an older vulnerable Flash Player version active

A system is affected if Adobe Flash Player is installed with a version at or below 27.0.0.159 (Desktop Runtime) or at or below 27.0.0.130/27.0.0.159 (other editions).

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 27.0.0.159
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to a version later than 27.0.0.159, or preferably remove Flash Player entirely given its end-of-life status and replace with modern web technologies.

Recommended fix High confidence

N/A - Adobe Flash Player reached End-of-Life on December 31, 2020. Upgrade to a supported solution (HTML5 video, native media players) or remove Flash entirely.

  1. Uninstall Adobe Flash Player from all affected systems using the operating system's package manager or the Adobe Flash Player uninstaller.
  2. For Enterprise Linux systems (Desktop, Server, Workstation 6.0), remove flash-plugin package via: yum remove flash-plugin or rpm -e flash-plugin
  3. Remove any remaining Flash Player browser plugins from all web browsers (Chrome, Firefox, Edge, etc.)
  4. Verify complete removal by checking that no Flash-related files remain in /usr/lib/flash-plugin, /usr/share/flash-plugin, or browser plugin directories
  5. Consider deploying Adobe's Flash Player End-of-Life removal tool if available for your platform
Caveat Removing Flash Player will cause Flash-based content, videos, and applications to no longer function. Ensure all business-critical Flash content has been migrated to modern alternatives before removal.

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

Fix this in Enterprise Linux Desktop Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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