dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2018-5008

HIGH · 7.5 CVSS v3.0 Published 2018-07-20
Fix available
A fix is available. Upgrade to after 30.0.0.113 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 30.0.0.113 and earlier versions have an Out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.

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

CVE-2018-5008 is an out-of-bounds read vulnerability in Adobe Flash Player versions 30.0.0.113 and earlier. The vulnerability allows an attacker to read memory contents beyond allocated buffers, potentially exposing sensitive information such as credentials, session tokens, or other data in memory.

MitigationUpdate Adobe Flash Player to version 30.0.0.120 or later, or remove Adobe Flash Player entirely if no longer required (Flash reached end-of-life in December 2020).

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:<= 30.0.0.113
Flash PlayerApplication
Affected:<= 30.0.0.113

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Verify Adobe Flash Player is installed
    On Windows, check Program Files for 'Adobe Flash Player' folder, or run 'Get-ItemProperty "HKLM:\SOFTWARE\Macromedia\FlashPlayer" -ErrorAction SilentlyContinue' in PowerShell. On Linux, check for '/usr/lib/flash-plugin' or rpm package 'flash-plugin'. On macOS, check /Library/Application Support/Adobe/Flash Player or browser plugins.
    Affected if Adobe Flash Player is found installed on the system
  2. Determine the installed Flash Player version
    In Windows, open 'Manage Add-ons' in browser or check HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion. In Linux, run 'rpm -q flash-plugin' or check version file in /usr/lib/flash-plugin. In browsers, navigate to 'about:plugins' or use 'https://helpx.adobe.com/flash-player.html' to detect.
    Affected if Version returned is 30.0.0.113 or earlier, or version cannot be determined but Flash is present
  3. Confirm the exact version number
    Cross-reference the discovered version against the affected range. The vulnerable versions are <= 30.0.0.113. If the system shows 30.0.0.113 exactly, it is within the affected range.
    Affected if Installed version is 30.0.0.113 or any version lower (e.g., 30.0.0.112, 29.0.0.x, etc.)
  4. Check if Flash is enabled in browsers
    Open each installed browser (Chrome, Firefox, Edge, Internet Explorer) and inspect the Add-ons or Extensions manager to confirm whether the Flash NPAPI/PPAPI plugin is active or set to 'Always Activate'.
    Affected if Flash Player plugin is installed and set to enabled or always active in any browser

The system is affected if Adobe Flash Player version 30.0.0.113 or earlier is installed and enabled in any browser, regardless of the operating system version listed in the affected products.

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.

From vendor data
Upgrade available Upgrade to a release after 30.0.0.113
Interim mitigation

Update Adobe Flash Player to version 30.0.0.120 or later, or remove Adobe Flash Player entirely if no longer required (Flash reached end-of-life in December 2020).

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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-2018-5008 — 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-2018-5008 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