dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2018-15967

HIGH · 7.5 CVSS v3.0 Published 2018-09-25
Fix available
A fix is available. Upgrade to after 31.0.0.108 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 versions 30.0.0.154 and earlier have a privilege escalation 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

Adobe Flash Player versions 30.0.0.154 and earlier contain a privilege escalation vulnerability that could allow an attacker to gain elevated privileges and access sensitive information. The vulnerability is exploitable through maliciously crafted Flash content.

MitigationUpdate Adobe Flash Player to a version newer than 30.0.0.154, or preferably uninstall Flash Player entirely since Adobe 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:<= 31.0.0.108
Flash PlayerApplication
Affected:<= 31.0.0.108

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 if Flash Player is installed
    Check for Flash plugin in browser (navigate to 'about:plugins' in Firefox or 'chrome://plugins' in Chrome, or check Add/Remove Programs on Windows, or run 'rpm -qa | grep -i flash' on Linux)
    Affected if Flash Player is present on the system
  2. Determine installed Flash version
    On Windows, check 'C:\Windows\System32\Macromed\Flash\Flash.ocx' properties or use browser plugin page. On Linux, run 'rpm -q flash-plugin' or check version in browser plugin list
    Affected if Version is 31.0.0.108 or earlier, or 30.0.0.154 or earlier (the fix was released after these versions)
  3. Confirm Flash is enabled in browsers
    In browser plugin settings, verify that Flash is not set to 'Never Activate' or 'Block'. Check browser plugin list for Flash status
    Affected if Flash is enabled and can be invoked by malicious content
  4. Check for RHEL flash-plugin package
    On Red Hat systems, run 'rpm -qa | grep -i flash' or 'yum list installed flash-plugin' to see if the Red Hat Flash plugin package is installed
    Affected if The flash-plugin package is installed with a version corresponding to vulnerable Flash releases

You are affected if Adobe Flash Player is installed, enabled, and running a version at or below 31.0.0.108 (or 30.0.0.154 based on the specific flaw description). If Flash is uninstalled or fully disabled in all browsers, you are not affected.

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 31.0.0.108
Interim mitigation

Update Adobe Flash Player to a version newer than 30.0.0.154, or preferably uninstall Flash Player entirely since Adobe reached end-of-life in December 2020.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

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