dbcve.org
FramemakerApplication · Adobe

CVE-2024-30292

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 versions 2020.5, 2022.3 and earlier contain an out-of-bounds write vulnerability during file parsing. An attacker can craft a malicious file that, when opened by a victim, triggers the vulnerability allowing arbitrary code execution in the context of the current user's privileges.

MitigationUpdate Adobe Framemaker to the latest version provided by Adobe's security advisory. Until patched, avoid opening untrusted or unexpected document files from unknown sources.

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. Confirm Adobe Framemaker is installed
    Check for the presence of Adobe Framemaker application: On Windows, look in Program Files for 'Adobe' folder containing Framemaker, or check Registry key HKLM\SOFTWARE\Adobe\Adobe Framemaker. On macOS, check /Applications for Adobe Framemaker.app.
    Affected if Adobe Framemaker software is present on the system
  2. Determine installed Framemaker version
    Open Framemaker and navigate to Help > About Adobe Framemaker to view the exact version number, or on Windows query the Registry key HKLM\SOFTWARE\Adobe\Adobe Framemaker\Version for the installed version string.
    Affected if Version cannot be determined or Framemaker is not found
  3. Compare version against affected ranges
    Compare the installed version number to the affected ranges: versions before 2020.6, or versions 2022.0 through 2022.3 are vulnerable. Version 2020.5 and earlier, or any 2022.x version below 2022.4, falls within the affected range.
    Affected if Installed version is 2020.5 or earlier, OR is 2022.0, 2022.1, 2022.2, or 2022.3
  4. Verify file parsing is accessible
    Confirm the application can open and parse document files (MIF, XML, or other Framemaker file formats). The vulnerability triggers during file parsing when a victim opens a maliciously crafted file.
    Affected if Users can open document files within Framemaker (this is the default behavior)

A user is affected if Adobe Framemaker is installed with a version that falls within 2020.5 and earlier, or 2022.0 through 2022.3.

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

Update Adobe Framemaker to the latest version provided by Adobe's security advisory. Until patched, avoid opening untrusted or unexpected document files from unknown sources.

Recommended fix High confidence

Adobe Framemaker 2020.6 or 2022.4 (or latest subsequent release)

  1. 1. Close Adobe Framemaker if it is currently running
  2. 2. Back up any important Framemaker documents before upgrading
  3. 3. Uninstall the current version of Adobe Framemaker
  4. 4. Download Adobe Framemaker 2020.6 (for 2020.x branch users) or 2022.4 (or latest 2022.x release) from the official Adobe website at helpx.adobe.com
  5. 5. Install the downloaded version following the on-screen prompts
  6. 6. After installation, verify the version by opening Framemaker and checking Help > About Adobe Framemaker
Caveat Standard upgrade; ensure compatibility with existing documents and any custom plugins or scripts

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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