dbcve.org
Media EncoderApplication · Adobe

CVE-2024-49552

HIGH · 7.8 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to 24.6.3 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Media Encoder versions 25.0, 24.6.3 and earlier are affected by a Heap-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 confidence

Adobe Media Encoder versions 25.0, 24.6.3 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a malicious file, potentially allowing arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Media Encoder to the latest patched version as released by Adobe to address this vulnerability.

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
Media EncoderApplication
Affected:< 24.6.3= 25.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Adobe Media Encoder is installed
    Check for the application in typical installation paths: Windows: C:\Program Files\Adobe\Adobe Media Encoder XX\ or C:\Program Files (x86)\Adobe\Adobe Media Encoder XX\; Mac: /Applications/Adobe Media Encoder XX.app
    Affected if The application is not found on the system, then the user is not affected by this CVE.
  2. Identify installed version on Windows
    Right-click the executable (AME.exe or Adobe Media Encoder.exe) in the installation folder, select Properties, then look at the Version tab. Alternatively, check the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Media Encoder\InstallPath or check version info in the executable directly.
    Affected if Version information cannot be retrieved or confirmed.
  3. Identify installed version on Mac
    Locate Adobe Media Encoder.app in /Applications, right-click and select Show Package Contents, navigate to Contents/Info.plist and check the CFBundleShortVersionString value, or right-click the app in Finder and select Get Info.
    Affected if Version information cannot be retrieved or confirmed.
  4. Compare version against affected ranges
    Compare the identified version number to the affected ranges: versions less than 24.6.3, or exactly version 25.0. The version format typically appears as "25.0" or "24.6.3" in the version properties.
    Affected if The installed version is less than 24.6.3 (such as 24.6.2, 24.5, 24.0, etc.) OR the installed version is exactly 25.0.

The user is affected if Adobe Media Encoder is installed and the version is either less than 24.6.3 or exactly 25.0, since these versions contain the heap-based buffer overflow vulnerability triggered by opening a malicious file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 24.6.3 or later
Fixed in 24.6.3
Interim mitigation

Update Adobe Media Encoder to the latest patched version as released by Adobe to address this vulnerability.

Recommended fix Moderate confidence

Media Encoder 25.1 or later (or 24.6.4 if released)

  1. 1. Close Adobe Media Encoder completely
  2. 2. Navigate to the Adobe Creative Cloud desktop application or visit adobe.com
  3. 3. Check for available updates to Adobe Media Encoder
  4. 4. Update to the latest available version (version 25.1 or later)
  5. 5. Verify the update was successful by checking the installed version in Media Encoder (Help > About Adobe Media Encoder)
Caveat Minor: Some legacy encoding presets may be deprecated in newer versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Media Encoder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49552 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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