dbcve.org
FramemakerApplication · Adobe

CVE-2024-30291

HIGH · 7.8 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 2020.6 / 2022.4 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.5, 2022.3 and earlier are affected by an out-of-bounds write 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 out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a malicious file. The vulnerability affects versions 2020.5, 2022.3 and earlier, and exploitation requires user interaction (opening a crafted file).

MitigationApply the vendor security update from Adobe to patch the vulnerability. Until patched, users should avoid opening untrusted or unexpected Framemaker files.

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.6>= 2022, < 2022.4

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. Check installed Framemaker version via About dialog
    Open Adobe Framemaker, then go to Help > About Adobe Framemaker to display the version number shown in the dialog window
    Affected if The displayed version is 2020.5 or earlier, or falls between 2022.0 and 2022.3 (inclusive)
  2. Check Framemaker version via Windows Registry
    Open Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Framemaker or HKEY_CURRENT_USER\SOFTWARE\Adobe\Adobe Framemaker, then locate the Version or ProductVersion value
    Affected if The version value is less than 2020.6, or is 2022.0 through 2022.3
  3. Check Framemaker version via Windows Programs and Features
    Open Control Panel > Programs and Features (or Settings > Apps > Apps & features on Windows 10/11), locate Adobe Framemaker in the list, and view the Installed version column
    Affected if The listed version is 2020.5 or earlier, or is 2022.0 through 2022.3
  4. Check Framemaker version on macOS
    Open Finder, navigate to /Applications/Adobe Framemaker, right-click and select Get Info, or launch Framemaker and check Adobe Framemaker > About Adobe Framemaker from the menu bar
    Affected if The version shown is 2020.5 or earlier, or is 2022.0 through 2022.3

You are affected if Adobe Framemaker version is 2020.5 or earlier, or any version from 2022.0 through 2022.3, and users open untrusted or unexpected 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.6 / 2022.4 or later
Fixed in 2020.62022.4
Interim mitigation

Apply the vendor security update from Adobe to patch the vulnerability. Until patched, users should avoid opening untrusted or unexpected Framemaker files.

Recommended fix High confidence

Framemaker 2020.6 or later; Framemaker 2022.4 or later

  1. 1. Determine the currently installed Adobe Framemaker version by opening Framemaker and navigating to Help > About Adobe Framemaker
  2. 2. If running version 2020.5 or earlier, download and install Framemaker 2020.6 or later from the Adobe website
  3. 3. If running version 2022.0 through 2022.3, download and install Framemaker 2022.4 or later from the Adobe website
  4. 4. Verify the installation was successful by checking Help > About Adobe Framemaker shows the updated version number
  5. 5. Ensure users are warned not to open untrusted .fm or other Framemaker document files from unknown sources
Caveat Standard minor version upgrade - no major breaking changes expected; Adobe updates typically include security fixes with routine stability improvements

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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