dbcve.org
FramemakerApplication · Adobe

CVE-2024-30287

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 2020.6 / 2022.4 or later.
See remediation →
58/100
Remediation priority · Elevated
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 Answer: are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 · moderate confidence

Adobe Framemaker versions 2020.5, 2022.3 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. An attacker can exploit this by tricking a user into opening a malicious file, potentially bypassing ASLR as an additional impact.

MitigationUpdate Adobe Framemaker to the latest patched version provided by Adobe. Until patched, advise users not to open untrusted files and consider applying additional endpoint monitoring for suspicious Framemaker file operations.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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. Determine installed Adobe Framemaker version
    Open Framemaker and navigate to Help > About Adobe Framemaker, or check the installed program version via Windows Programs and Features / macOS Applications folder
    Affected if Version displayed is 2020.5 or earlier, or falls between 2022.0 and 2022.3 inclusive
  2. Confirm version is within affected ranges
    Compare your installed version number against: (1) any release before 2020.6, or (2) any release from 2022.0 through 2022.3
    Affected if Installed version is < 2020.6 OR (>= 2022.0 AND < 2022.4)
  3. Verify Framemaker application is present
    Check if Adobe Framemaker is installed on the system by looking for the executable (framemaker.exe on Windows, Adobe Framemaker in Applications on macOS)
    Affected if The application exists and the version falls into the affected ranges from step 2
  4. Assess user exposure to file-based attack vector
    Determine whether users in your environment routinely open .fm, .book, or other Framemaker document files from external or untrusted sources
    Affected if Users open Framemaker documents from untrusted or unknown sources without prior validation

You are affected if Adobe Framemaker version is either 2020.5/earlier or between 2022.0 and 2022.3, and users could potentially open malicious Framemaker 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

Update Adobe Framemaker to the latest patched version provided by Adobe. Until patched, advise users not to open untrusted files and consider applying additional endpoint monitoring for suspicious Framemaker file operations.

Recommended fix High confidence

Adobe Framemaker 2020.6 or later (for 2020.x line); Adobe Framemaker 2022.4 or later (for 2022.x line)

  1. 1. Identify the current Adobe Framemaker version by navigating to Help > About Adobe Framemaker
  2. 2. For Framemaker 2020.x line (versions before 2020.6): Download and install Adobe Framemaker 2020.6 or later from the Adobe website
  3. 3. For Framemaker 2022.x line (versions 2022.0 through 2022.3): Download and install Adobe Framemaker 2022.4 or later from the Adobe website
  4. 4. After installation, verify the version by checking Help > About Adobe Framemaker to confirm the patch was applied
  5. 5. Ensure users are warned not to open untrusted or unexpected .fm, .mif, or other Framemaker document files
Caveat Standard minor version upgrade - minimal risk; however, test critical documents for compatibility with the new version before broad deployment in production environments

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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