CVE-2018-4877
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 · uneditedA use-after-free vulnerability was discovered in Adobe Flash Player before 28.0.0.161. This vulnerability occurs due to a dangling pointer in the Primetime SDK related to media player's quality of service functionality. A successful attack can 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's Primetime SDK, specifically in the media player's quality of service functionality. The vulnerability stems from a dangling pointer that persists after memory is freed, allowing an attacker to manipulate the freed memory and achieve arbitrary code execution.
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< 28.0.0.161CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Verify if Adobe Flash Player is installedCheck for the presence of Flash Player NPAPI plugin. On Windows: look for 'C:\Windows\System32\Macromed\Flash' folder or check Add/Remove Programs. On Linux: check /usr/lib/flash-plugin or /opt/flash-player. On macOS: check /Library/Internet Plug-Ins/Flash Player.pluginAffected if Adobe Flash Player is present on the system
-
Determine installed Adobe Flash Player versionOpen a web browser and navigate to 'about:flash' in the address bar, or visit Adobe's version check page at https://www.adobe.com/software/flash/about/, or check the file version property of the Flash DLL (e.g., NPSWF32.dll or FlashPlayerPlugin_*.exe)Affected if The displayed version is earlier than 28.0.0.161 (any version < 28.0.0.161)
-
Check for Red Hat Enterprise Linux 6.0 with Flash PlayerOn RHEL systems, run 'cat /etc/redhat-release' to confirm the OS version, then check for installed Flash packages using 'rpm -qa | grep -i flash' or 'dpkg -l | grep -i flash'Affected if Running Red Hat Enterprise Linux Desktop, Server, or Workstation version 6.0 AND Adobe Flash Player is installed
-
Verify Primetime SDK component presenceThis vulnerability exists in the Primetime SDK quality of service module bundled with Flash Player. Confirm Flash Player is the Primetime-enabled variant by examining the installed Flash package details or DLL metadataAffected if Any installed version of Adobe Flash Player below 28.0.0.161 contains the affected Primetime SDK component
You are affected if Adobe Flash Player version 28.0.0.161 or later is NOT installed, or if running RHEL 6.0 with any version of Flash Player present.
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.
dbcve · scoped28.0.0.161
Update Adobe Flash Player to version 28.0.0.161 or later; if Flash Player cannot be updated due to end-of-life status, remove it entirely or implement compensating controls such as network segmentation and application whitelisting.
Flash Player 28.0.0.161 or later (flash-plugin package)
- 1. Check the current Flash Player version by navigating to 'https://helpx.adobe.com/flash-player.html' or typing 'about:flash' in a browser address bar
- 2. For Red Hat Enterprise Linux systems: Run 'sudo yum update flash-plugin' to update to the latest available version
- 3. For Debian/Ubuntu systems: Run 'sudo apt-get update && sudo apt-get install flashplugin-installer' or 'adobe-flashplugin'
- 4. Verify the installation completed successfully by checking the Flash Player version again
- 5. Restart any running browsers to ensure the new Flash Player plugin is loaded
- 6. As a long-term security measure, consider disabling or removing Flash Player entirely since it has reached end-of-life and poses ongoing security risks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-4877 — 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-2018-4877 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