Enterprise Linux DesktopOperating system · Redhat
CVE-2018-15982
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 · uneditedFlash Player versions 31.0.0.153 and earlier, and 31.0.0.108 and earlier have a use after free vulnerability. 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 · moderate confidenceAdobe Flash Player contains a use-after-free vulnerability that allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability affects versions 31.0.0.153 and earlier, as well as version 31.0.0.108 and earlier.
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
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0<= 31.0.0.153<= 31.0.0.108CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Adobe Flash Player browser plugin is presentSearch for the Flash plugin file in common browser plugin directories. On Linux, check paths like /usr/lib/mozilla/plugins/, /usr/lib64/mozilla/plugins/, and ~/.mozilla/plugins/ for files named libflashplayer.so or similar. On Windows, check browser plugin directories for NPSWF32.dll or FlashPlayerPlugin_*.*.Affected if The plugin file exists in any browser plugin directory
-
Determine the installed Flash Player versionFor the found plugin file, run: on Linux, 'rpm -qa | grep -i flash' to check for installed RPM packages; on Windows, right-click the DLL file and view Properties > Details for the File Version. Alternatively, in Firefox enter 'about:plugins' in the address bar to see Flash version information.Affected if The version displayed matches or is earlier than 31.0.0.153 (or 31.0.0.108 for installer packages)
-
Check for Flash Player installer packagesRun 'rpm -qa | grep -i flash' on RHEL systems to list any installed Flash-related RPM packages including installer components. Also check for packages named like flash-plugin or adobe-release.Affected if An installed package version is 31.0.0.153 or earlier, or 31.0.0.108 or earlier for installer variants
-
Verify browser plugin enablement statusOpen the browser and navigate to 'about:plugins' (Firefox) or 'chrome://plugins' (Chrome) to confirm the Flash plugin is enabled and loaded. Check if the plugin is present and active in any installed web browsers.Affected if The Flash plugin shows as enabled/active in browser plugin lists
You are affected if Adobe Flash Player (or its installer) is installed and its version is 31.0.0.153 or earlier, or 31.0.0.108 or earlier for installer variants, and the browser plugin is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe Flash Player to a version later than 31.0.0.153 or 31.0.0.108 to remediate the use-after-free vulnerability and prevent arbitrary code execution.
Flash Player 31.0.0.154 or later
- 1. Verify the current Flash Player version by navigating to 'About Flash Player' in the player settings or checking the version through the system's software management tool.
- 2. For Windows/macOS systems: Download Flash Player 31.0.0.154 or later from the official Adobe Flash Player distribution channel (note: Adobe ended Flash Player support on December 31, 2020).
- 3. For Linux systems: If Flash Player is installed through the package manager, use the appropriate package update command (e.g., 'yum update' or 'dnf update' for Red Hat-based systems) to obtain the patched version.
- 4. Alternatively, if the system still has Flash Player installed post-December 2020, consider uninstalling/removing Flash Player entirely as it is no longer supported and poses security risks.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Linux Desktop
Exploited in the wild — priority engagement
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2018-15982 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-15982 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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