dbcve.org
FramemakerApplication · Adobe

CVE-2024-47421

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 out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 out-of-bounds read vulnerability when parsing specially crafted files. The vulnerability allows reading past the end of allocated memory structures, which can potentially be leveraged to achieve arbitrary code execution in the context of the current user. Successful exploitation requires user interaction to open a malicious file.

MitigationApply the vendor-supplied security patch for Adobe Framemaker to upgrade to a fixed version. Until patched, advise users not to open untrusted or unexpected files, and consider deploying additional file-type restrictions or sandboxing for the application.

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. Locate Adobe Framemaker installation
    Check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Framemaker or HKEY_CURRENT_USER\SOFTWARE\Adobe\Framemaker for the Version key, or locate the framemaker.exe file and right-click to view Properties > Details for the Product Version
    Affected if Adobe Framemaker is installed on the system
  2. Identify installed version number
    Read the Version value from the registry key or the Product Version field from the executable properties dialog
    Affected if The version cannot be determined or does not match expected Adobe Framemaker versioning
  3. Compare against affected version ranges
    Compare your identified version against: 2020.6 and earlier (any 2020.x version below 2020.7), OR any 2022.x version from 2022.0 through 2022.4
    Affected if The installed version is 2020.6 or earlier, OR falls between 2022.0 and 2022.4 inclusive
  4. Verify file parsing is enabled
    Adobe Framemaker natively supports opening and parsing .fm and other document files; no special feature toggle is required - the vulnerability exists in the core file parsing functionality
    Affected if The application can open and parse document files, which is the default behavior

If Adobe Framemaker version is 2020.6 or earlier, or any version from 2022.0 through 2022.4, the environment is vulnerable when processing untrusted .fm or related 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

Apply the vendor-supplied security patch for Adobe Framemaker to upgrade to a fixed version. Until patched, advise users not to open untrusted or unexpected files, and consider deploying additional file-type restrictions or sandboxing for the application.

Recommended fix High confidence

Framemaker 2020.7 or later for the 2020.x line; Framemaker 2022.5 or later for the 2022.x line

  1. Identify the currently installed Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. If the version is 2020.6 or earlier, upgrade to Framemaker 2020.7 or later
  3. If the version is 2022.0 through 2022.4, upgrade to Framemaker 2022.5 or later
  4. Download the updated version from the official Adobe website or through your organization's software distribution channel
  5. After installation, verify the new version by checking Help > About Adobe Framemaker
Caveat Standard upgrade considerations apply - review Adobe's release notes for the new version for any feature changes or known issues before deploying

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

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

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 locally
dbcve dependency scanner

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