Enterprise Linux DesktopOperating system · Redhat

CVE-2019-7837

HIGH · 8.8 CVSS v3.0 Published 2019-05-22
Fix available
A fix is available. Upgrade to after 32.0.0.171 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 32.0.0.171 and earlier, 32.0.0.171 and earlier, and 32.0.0.171 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 · high confidence

Use-after-free vulnerability in Adobe Flash Player allowing memory to be accessed after being freed, potentially enabling arbitrary code execution. The flaw exists in versions 32.0.0.171 and earlier.

MitigationUpdate to a newer Flash Player version beyond 32.0.0.171, or preferably remove/disable Flash Player entirely since it 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:<= 32.0.0.171
Flash PlayerApplication
Affected:<= 32.0.0.171

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

CVSS:3.0/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Adobe Flash Player is installed
    On Windows, check Program Files for Adobe Flash Player folders or check browser extensions. On Linux, use package manager (dpkg -l | grep flash or rpm -qa | grep flash) or check /usr/lib/flash-plugin. On macOS, check /Library/Internet Plug-Ins for Flash Player.
    Affected if Flash Player is found installed on the system
  2. Determine the installed Flash Player version
    On Windows, open Flash Player in Windows Programs and Features or check the version via the Flash Player Help > About Adobe Flash Player. In browsers, navigate to about:plugins (Firefox) or chrome://plugins (Chrome) to see version. On Linux, run rpm -q flash-plugin or check the version file in the installation directory.
    Affected if Version cannot be determined or is 32.0.0.171 or earlier
  3. Compare installed version to affected range
    Compare the discovered version number to the affected range: any version less than or equal to 32.0.0.171 is vulnerable. Note the exact version number displayed.
    Affected if Installed version is 32.0.0.171 or any earlier version (e.g., 32.0.0.156, 31.0.0.0, etc.)
  4. Verify Flash Player is enabled in browsers
    Check browser plugin settings to confirm Flash Player is enabled. In Firefox, go to Add-ons > Plugins. In Chrome, go to chrome://settings/content. In Edge, go to edge://settings/content.
    Affected if Flash Player is enabled and the version is within the affected range

The system is affected if Adobe Flash Player is installed with any version <= 32.0.0.171 and is enabled for use in any browser or application.

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

Update to a newer Flash Player version beyond 32.0.0.171, or preferably remove/disable Flash Player entirely since it reached end-of-life in December 2020.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,064.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7837 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-7837 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