dbcve.org
FramemakerApplication · Adobe

CVE-2024-47425

HIGH · 7.8 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 2020.7 / 2022.5 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
Adobe Framemaker versions 2020.6, 2022.4 and earlier are affected by an Integer Underflow (Wrap or Wraparound) 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 Framemaker versions 2020.6, 2022.4 and earlier contain an integer underflow (wraparound) vulnerability that can be triggered when parsing a specially crafted malicious file, potentially allowing arbitrary code execution in the context of the current user.

MitigationUsers should avoid opening untrusted files and organizations should deploy the vendor patch to update to a fixed version of Adobe Framemaker.

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
FramemakerApplication
Affected:< 2020.7>= 2022, < 2022.5

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 Framemaker is installed
    Check for Adobe Framemaker in the list of installed applications via Control Panel > Programs and Features, or use command 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' on Windows
    Affected if Adobe Framemaker appears in the installed programs list
  2. Determine the installed Framemaker version
    Open Adobe Framemaker, then go to Help > About Adobe Framemaker to view the exact version number, or check the Windows registry key HKLM\SOFTWARE\Adobe\FrameMaker\Version for the installed version value
    Affected if The displayed version is a specific number that can be compared against the affected ranges
  3. Compare installed version against affected ranges
    If version shows as 2020.x, check if it is less than 2020.7. If version shows as 2022.x, check if it is less than 2022.5. Any version before 2020.7 or between 2022.0 and 2022.4 inclusive is affected
    Affected if Installed version is < 2020.7 OR (installed version >= 2022.0 AND installed version < 2022.5)
  4. Confirm file parsing is the attack vector
    This vulnerability is triggered when Framemaker parses specially crafted files. Since file parsing is core Framemaker functionality, any use of the software to open document files could trigger the flaw if a malicious file is opened
    Affected if The software is used to open or parse document files, as the vulnerability requires parsing a maliciously crafted file

The environment is affected if Adobe Framemaker is installed and the installed version falls below 2020.7 or is in the 2022.0 to 2022.4 range, since these versions contain the integer underflow vulnerability when parsing files.

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 2020.7 / 2022.5 or later
Fixed in 2020.72022.5
Interim mitigation

Users should avoid opening untrusted files and organizations should deploy the vendor patch to update to a fixed version of Adobe Framemaker.

Recommended fix High confidence

Framemaker 2020.7 or later; Framemaker 2022.5 or later

  1. 1. Close Adobe Framemaker if it is currently open
  2. 2. Back up any important documents and custom configurations
  3. 3. For Framemaker 2020.x users: Navigate to the Adobe Creative Cloud desktop app or visit helpx.adobe.com to download Framemaker 2020.7 or later
  4. 4. For Framemaker 2022.x users: Navigate to the Adobe Creative Cloud desktop app or visit helpx.adobe.com to download Framemaker 2022.5 or later
  5. 5. Run the installer and follow the on-screen prompts to complete the upgrade
  6. 6. After installation, verify the version by opening Framemaker and checking Help > About Adobe Framemaker
  7. 7. Test critical workflows with the new version before deploying to production users
Caveat Minimal risk - point version upgrades within the same release typically preserve compatibility with existing documents and configurations

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47425 — 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-47425 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