dbcve.org
FramemakerApplication · Adobe

CVE-2024-47424

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 Overflow 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 contains an integer overflow vulnerability where a specially crafted file can cause memory corruption leading to arbitrary code execution in the context of the current user. The vulnerability is triggered when a user opens a malicious file, requiring user interaction for exploitation.

MitigationUpdate Adobe Framemaker to the latest version and exercise caution when opening files from untrusted sources. Organizations should deploy patches through their software distribution mechanisms and verify successful installation.

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 installation by looking for the executable in common installation paths such as C:\Program Files\Adobe\Adobe Framemaker or C:\Program Files (x86)\Adobe\Adobe Framemaker, or use system inventory tools to query installed software.
    Affected if Adobe Framemaker is present on the system
  2. Determine the installed Framemaker version
    Open Adobe Framemaker, then go to Help > About Adobe Framemaker to display the version number, or check the Windows registry under HKLM\SOFTWARE\Adobe\Framemaker\Version for the version value.
    Affected if A version number is displayed or found in the registry
  3. Compare version against affected ranges
    Compare the installed version to the affected ranges: versions prior to 2020.7, and versions 2022.0 through 2022.4 are vulnerable. Versions 2020.7 through 2021.x and version 2022.5 or later are not affected.
    Affected if Installed version is less than 2020.7, OR installed version is 2022.0 through 2022.4

A user is affected if Adobe Framemaker is installed with a version prior to 2020.7 or between 2022.0 and 2022.4, and the user opens untrusted MIF or other supported document 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

Update Adobe Framemaker to the latest version and exercise caution when opening files from untrusted sources. Organizations should deploy patches through their software distribution mechanisms and verify successful installation.

Recommended fix High confidence

Adobe Framemaker 2020.7 or later; Adobe Framemaker 2022.5 or later

  1. Identify the currently installed Adobe Framemaker version via Help > About Adobe Framemaker
  2. If running version 2020.6 or earlier, upgrade to version 2020.7 or later
  3. If running version 2022.0 through 2022.4, upgrade to version 2022.5 or later
  4. Download the upgrade from the official Adobe website or through your organization's Adobe licensing portal
  5. Install the upgrade following standard Adobe installation procedures
  6. Verify the installed version after upgrade matches the expected fixed release
Caveat Standard upgrade considerations apply - review Adobe's release notes for the target version for any feature changes or compatibility notes

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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