dbcve.org
FramemakerApplication · Adobe

CVE-2024-30286

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 · high confidence

Adobe Framemaker contains an out-of-bounds read vulnerability where parsing a specially crafted malicious file causes the software to read memory outside allocated buffer boundaries. This can expose sensitive memory contents and potentially facilitate bypass of ASLR and other memory protection mitigations. The attack requires user interaction—the victim must open the malicious file.

MitigationApply the vendor-provided security patch from Adobe for the affected Framemaker versions. Additionally, enforce policies prohibiting users from opening files from untrusted or unknown sources, and consider email/web filtering to block delivery of suspicious file attachments.

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. Locate installed Adobe Framemaker version
    On Windows, open Control Panel > Programs and Features, or go to Help > About Adobe Framemaker within the application. On macOS, navigate to Applications > Adobe Framemaker and select Get Info, or use Help > About within the app.
    Affected if The installed version cannot be determined or the product is present on the system
  2. Compare version against affected ranges
    Identify the full version number (e.g., 2022.1, 2020.5). Check if the version is less than 2020.6, OR if it falls between 2022.0 and 2022.3 (inclusive). Versions 2020.6 through 2021.x and 2022.4 and later are NOT affected.
    Affected if The installed version is < 2020.6 OR >= 2022.0 AND < 2022.4

If Adobe Framemaker is installed and the version falls within the affected ranges (< 2020.6, or >= 2022.0 and < 2022.4), the system is vulnerable to out-of-bounds read when parsing malicious 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-provided security patch from Adobe for the affected Framemaker versions. Additionally, enforce policies prohibiting users from opening files from untrusted or unknown sources, and consider email/web filtering to block delivery of suspicious file attachments.

Recommended fix Moderate confidence

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

  1. 1. Check current Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. 2. If running version 2020.5 or earlier, upgrade to Adobe Framemaker 2020.6 or later
  3. 3. If running version 2022.0 through 2022.3, upgrade to Adobe Framemaker 2022.4 or later
  4. 4. Download the updated version from the official Adobe website (helpx.adobe.com) or through your organization's Adobe license portal
  5. 5. Close all Framemaker instances and run the installer
  6. 6. After installation, verify the new version by checking Help > About Adobe Framemaker
Caveat Standard upgrade - review Adobe's release notes for any documentation format changes between versions

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-30286 — 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-30286 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