CVE-2021-28580
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 · uneditedMedium by Adobe version 2.4.5.331 (and earlier) is affected by a buffer overflow vulnerability when parsing a crafted file. An unauthenticated attacker could leverage this vulnerability to achieve remote code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 · moderate confidenceAdobe Medium version 2.4.5.331 and earlier contains a buffer overflow vulnerability when parsing specially crafted files. Successful exploitation allows an unauthenticated attacker to achieve remote code execution in the context of the current user, but requires victim interaction (opening a malicious file).
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<= 2.4.5.331CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Confirm Adobe Medium installationOn Windows, check for Adobe Medium in Program Files or scan registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Adobe Medium'. On macOS, check /Applications for Adobe Medium.appAffected if Adobe Medium software is found on the system
-
Retrieve installed version numberOn Windows, locate the Adobe Medium uninstall registry key and read the DisplayVersion value, or right-click the executable in Program Files and view Properties > Details. On macOS, right-click Adobe Medium.app, select Get Info, and read the Version fieldAffected if Unable to determine version but software is present
-
Compare against vulnerable version rangeCompare your extracted version against the affected range: any version numbered 2.4.5.331 or earlier is vulnerableAffected if Installed version is 2.4.5.331 or any version number lower than 2.4.5.331
System is affected if Adobe Medium version 2.4.5.331 or earlier is installed and capable of opening files
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 · scopedUsers should avoid opening files from untrusted or unknown sources. Organizations should identify and upgrade Adobe Medium installations to the latest patched version, or uninstall the software if not required.
Adobe Medium version 2.4.5.332 or later (or latest available version)
- Navigate to the Adobe Creative Cloud desktop application or Adobe Medium download page
- Check the current installed version of Adobe Medium (formerly Adobe Creative Cloud Express)
- If the installed version is 2.4.5.331 or earlier, initiate an update to obtain the latest version
- Alternatively, uninstall the current version and download the latest version from Adobe's official website
- After updating, verify the new version number to confirm the patch has been applied
- Ensure users are warned not to open untrusted or unsolicited files to mitigate the user interaction requirement for exploitation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28580 — 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-2021-28580 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