Enterprise Linux DesktopOperating system · Redhat
CVE-2019-7845
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.192 and earlier, 32.0.0.192 and earlier, and 32.0.0.192 and earlier have an 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 confidenceThis is a use-after-free vulnerability in Adobe Flash Player versions 32.0.0.192 and earlier. The flaw allows attackers to exploit freed memory references, potentially executing arbitrary code remotely without authentication, as indicated by the high CVSS score of 8.8.
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<= 32.0.0.192CVSS 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.1/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: Look for 'Flash Player' in Control Panel > Programs and Features, or check C:\Windows\System32\Macromed\Flash\ for presence of files. On Linux: Run 'rpm -qa | grep -i flash' or 'dpkg -l | grep -i flash' to list Flash packages.Affected if Adobe Flash Player package or plugin files are found on the system
-
Retrieve installed Flash Player version on WindowsRight-click the FlashPlayerPlugin_*.exe file in the Flash directory, select Properties, then view the Details tab for version information.Affected if The version displayed is 32.0.0.192 or earlier
-
Retrieve installed Flash Player version on Linux (RHEL)Run 'rpm -q flash-plugin' to query the flash-plugin package version.Affected if The version output shows 32.0.0.192 or earlier, or the package is missing version info but is present
-
Check browser plugins for FlashIn Firefox: Navigate to about:addons > Plugins. In Chrome: Navigate to chrome://plugins. Look for 'Shockwave Flash' entry and note its version.Affected if A Shockwave Flash plugin is listed with version 32.0.0.192 or earlier
If Adobe Flash Player is present on the system with any version up to and including 32.0.0.192, the system is vulnerable to this use-after-free flaw.
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 dataAdobe Flash Player reached end-of-life in December 2020 and should be completely removed from all systems. If Flash is required for legacy applications, isolate those systems and apply vendor-provided patches if available.
Fix this in Enterprise Linux Desktop
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7845 — 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-7845 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