CVE-2024-20772
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 · uneditedMedia Encoder versions 24.2.1, 23.6.4 and earlier are affected by a Stack-based Buffer Overflow vulnerability that could result in arbitrary 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 · high confidenceStack-based buffer overflow vulnerability in Adobe Media Encoder that allows arbitrary code execution when a victim opens a malicious file. The flaw exists in handling file input and can be exploited to execute arbitrary code in the context of the current user.
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< 23.6.5>= 24.0, < 24.3CVSS 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.
-
Verify Adobe Media Encoder installationCheck for Adobe Media Encoder in system program directories. On Windows: Look in C:\Program Files\Adobe\Adobe Media Encoder or C:\Program Files (x86)\Adobe\Adobe Media Encoder. On macOS: Check /Applications for Adobe Media Encoder.appAffected if Adobe Media Encoder is present on the system
-
Retrieve installed version numberOn Windows: Right-click the executable (AME.exe) in the installation folder, select Properties, then view the Details tab for Product Version. Alternatively, open Adobe Media Encoder and go to Help > About Adobe Media Encoder to display the version.Affected if Version cannot be determined or AME is not installed
-
Compare version against affected rangesNote the full version number (for example 23.6.0, 24.0, 24.2). Compare numerically: versions below 23.6.5 are affected (23.0 through 23.6.4), and versions 24.0 through 24.2 are affected. Versions 23.6.5 and above, and 24.3 and above, are not affected.Affected if Installed version is less than 23.6.5 OR falls between 24.0 and 24.2 inclusive
-
Assess exposure to malicious file vectorDetermine if the system routinely processes media files from external or untrusted sources. The vulnerability triggers when Adobe Media Encoder opens a specially crafted malicious file. Review workflow for file import from email attachments, downloads, or network shares.Affected if Users routinely open media files from untrusted sources using Adobe Media Encoder
If Adobe Media Encoder is installed and the version falls below 23.6.5 or between 24.0 and 24.2, the environment is vulnerable when processing maliciously crafted media 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 · scoped23.6.524.3
Update Adobe Media Encoder to the latest patched version provided by Adobe to remediate this vulnerability.
Adobe Media Encoder 23.6.5 (for 23.x line) or 24.3+ (for 24.x line)
- Open Adobe Creative Cloud desktop application or navigate to Adobe Media Encoder download page
- Ensure you are signed in with your Adobe ID and license is active
- Check current installed version via Help > About Adobe Media Encoder
- For version 23.x users: Upgrade to version 23.6.5 or later
- For version 24.x users: Upgrade to version 24.3 or later
- Download and install the updated version
- Restart the application after installation
- Verify the version number reflects the update (Help > About Adobe Media Encoder)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20772 — 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-2024-20772 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