Enterprise Linux DesktopOperating system · Redhat
CVE-2018-5002
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 · uneditedAdobe Flash Player versions 29.0.0.171 and earlier have a Stack-based buffer overflow vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
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 29.0.0.171 and earlier contain a stack-based buffer overflow vulnerability. This memory corruption flaw allows an attacker to overwrite stack memory boundaries, potentially enabling arbitrary code execution with the current user's privileges.
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<= 29.0.0.171<= 29.0.0.171CVSS 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 Flash Player is installed in ChromeNavigate to chrome://components/ and look for 'Adobe Flash Player' entry under 'Plug-ins'. Note the version listed.Affected if Adobe Flash Player appears in the list with version 29.0.0.171 or earlier
-
Check if Flash Player is installed in FirefoxNavigate to about:addons, click 'Plugins', and look for 'Shockwave Flash'. Note the version displayed.Affected if Shockwave Flash appears with version 29.0.0.171 or earlier
-
Check for Flash Player on Windows systemsSearch for 'flashplayerapp.exe' or 'pepperflash' in Program Files and Program Files (x86) directories, or check C:\Windows\System32\Macromed\Flash for npctrl.dll or similar Flash DLL files.Affected if Flash Player DLL or executable exists with version 29.0.0.171 or earlier (right-click file, select Properties > Details to view version)
-
Check for Flash Player on Linux systemsRun command 'rpm -q flash-player' or 'dpkg -l | grep flash' to list installed Flash packages, or check /usr/lib/adobe-flashplugin/ directory.Affected if Flash Player package is installed with version 29.0.0.171 or earlier as shown in the package version
A user is affected if Adobe Flash Player is present in any browser or system location with a version number at or below 29.0.0.171.
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.
From vendor dataUpdate Adobe Flash Player to a version newer than 29.0.0.171, or preferably remove/disable Flash Player entirely as it reached end-of-life in December 2020 and no longer receives security updates.
Fix this in Enterprise Linux Desktop
Exploited in the wild — priority engagement
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5002 — 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-5002 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