dbcve.org
FramemakerApplication · Adobe

CVE-2022-28822

HIGH · 7.8 CVSS v3.0 Published 2022-05-13
Fix available
A fix is available. Upgrade to after 2020.0.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 2029u8 (and earlier) and 2020u4 (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 2029u8 and earlier, as well as 2020u4 and earlier, contain an out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a malicious file. The vulnerability stems from improper bounds checking during file parsing, enabling memory corruption that can be leveraged by attackers.

MitigationApply the vendor security update to obtain patched versions of Adobe Framemaker (newer than 2029u8 and 2020u4). Avoid opening untrusted or unexpected files from unknown sources until the patch is applied.

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:>= 2019, <= 2019.0.8>= 2020, <= 2020.0.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.0/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 for Adobe Framemaker in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or look in typical installation paths such as C:\Program Files\Adobe\Adobe FrameMaker*
    Affected if Adobe Framemaker is found on the system
  2. Identify installed Framemaker version
    Right-click on the Framemaker executable (framemaker.exe) in the installation folder, select Properties, and view the Details tab for the Product Version field; alternatively, query the registry key for the installed version
    Affected if The version displayed is 2019.0.x where x is 0 through 8, or 2020.0.x where x is 0 through 4
  3. Verify exact version number
    Open Adobe Framemaker, go to Help > About Adobe Framemaker to confirm the precise version and update number displayed
    Affected if The version shows 2019.0.8 or earlier, or 2020.0.4 or earlier
  4. Confirm vulnerability trigger condition
    Note that the vulnerability requires a user to open a maliciously crafted file in Framemaker; the affected version alone is not sufficient without file interaction
    Affected if A user with the vulnerable version opens untrusted or crafted files

A user is affected if Adobe Framemaker version 2019.0.8 or earlier, or version 2020.0.4 or earlier, is installed and a user opens a malicious file.

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 a release after 2020.0.4
Interim mitigation

Apply the vendor security update to obtain patched versions of Adobe Framemaker (newer than 2029u8 and 2020u4). Avoid opening untrusted or unexpected files from unknown sources until the patch is applied.

Recommended fix Moderate confidence

Upgrade to a Framemaker version newer than 2019.0.8 and 2020.0.4 (e.g., 2019.0.9 or later, 2020.0.5 or later, or the latest available release)

  1. 1. Verify current Adobe Framemaker installation by opening the application and navigating to Help > About Adobe Framemaker to confirm the exact version number.
  2. 2. If version is 2019.0.8 or earlier, or 2020.0.4 or earlier, the installation is vulnerable.
  3. 3. Close Adobe Framemaker completely before proceeding with the update.
  4. 4. Download the latest version of Adobe Framemaker from the official Adobe website or your organization's software distribution point.
  5. 5. Run the installer and follow the on-screen prompts to complete the installation.
  6. 6. After installation completes, launch Framemaker and verify the new version by checking Help > About Adobe Framemaker.
  7. 7. Ensure the installed version is newer than 2019.0.8 and 2020.0.4 to confirm the vulnerability is addressed.
Caveat Review Adobe's release notes for the target version to check for feature changes or compatibility considerations with existing documents and workflows

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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