CVE-2018-15981
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.148 and earlier have a type confusion 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 · high confidenceAdobe Flash Player versions 31.0.0.148 and earlier contain a type confusion vulnerability that allows attackers to execute arbitrary code by manipulating object types during runtime, potentially leading to complete system compromise.
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= 6.0= 6.0= 6.0<= 31.0.0.148<= 31.0.0.148CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 is installed on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Macromedia\FlashPlayer, then look for the Version valueAffected if The Version value exists and is less than or equal to 31.0.0.148, or the key exists with no version specified (indicating an older install)
-
Check for Flash Player plugin in web browsers on WindowsFor Chrome: Navigate to chrome://plugins and look for Adobe Flash Player. For Firefox: Navigate to about:addons and check the Plugins section. For Edge/IE: Check C:\Windows\System32\Macromed\Flash for the Flash.ocx fileAffected if Flash Player plugin is present in any browser and the version is 31.0.0.148 or earlier
-
Check for Flash Player on Linux systemsRun rpm -qa | grep -i flash or check /usr/lib/flash-plugin/ for Red Hat systems. Also check browser plugin directories: ~/.mozilla/plugins/ and /usr/lib/mozilla/plugins/Affected if Flash Player package is installed with a version at or below 31.0.0.148
-
Check for Flash Player on macOSCheck /Library/Internet Plug-Ins/ for Flash Player.plugin. Also check ~/Library/Internet Plug-Ins/ for user-installed Flash. Run: defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion to get versionAffected if Flash Player plugin exists and version is 31.0.0.148 or earlier
-
Verify Adobe Flash Player version via NPAPI/PPAPI DLLOn Windows, right-click the Flash.ocx or FlashPlayerPlugin_*.dll file in System32 or the browser plugin folder, select Properties, and check the File Version tab. Compare against 31.0.0.148Affected if The DLL file exists and shows version 31.0.0.148 or lower
If Adobe Flash Player is present on the system and its version number is 31.0.0.148 or any earlier version, the system is affected by this vulnerability.
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 · scopedSince Adobe Flash Player has been deprecated and reached end-of-life, the primary remediation is to completely uninstall or remove Flash Player from all affected systems; where removal is not feasible, implement defense-in-depth controls such as network segmentation and application whitelisting.
- Remove Flash Player from the system using the appropriate method for the operating system.
- For Windows: Use Control Panel > Programs and Features to uninstall Adobe Flash Player.
- For macOS: Remove the /Library/Internet Plug-Ins/FlashPlayer.plugin directory and related files.
- For Linux: Remove flash-player-properties and related packages using the package manager (e.g., yum remove flash-plugin or apt remove flashplugin-installer).
- Ensure all browser plugins related to Flash are also disabled or removed.
- Verify removal by checking that Flash is no longer listed in browser extensions or add-ons.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15981 — 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-15981 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