CVE-2019-7837
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 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 confidenceUse-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.
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<= 32.0.0.171<= 32.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Adobe Flash Player is installedOn 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
-
Determine the installed Flash Player versionOn 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
-
Compare installed version to affected rangeCompare 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.)
-
Verify Flash Player is enabled in browsersCheck 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.
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 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.
- Consultation4.0 h
- Implementation6.0 h
- Testing2.0 h
- Review / QA2.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-7837 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