dbcve.org
FramemakerApplication · Adobe

CVE-2022-28828

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

Out-of-bounds write vulnerability in Adobe Framemaker versions 2029u8 and earlier, and 2020u4 and earlier. The vulnerability allows arbitrary code execution in the context of the current user when a victim opens a specially crafted malicious file.

MitigationUpdate Adobe Framemaker to the latest patched version; avoid opening untrusted or unexpected 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:>= 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. Verify Adobe Framemaker is installed
    Check for Adobe Framemaker in the list of installed programs via Windows Settings > Apps & Features, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Adobe Framemaker'
    Affected if Adobe Framemaker is present on the system
  2. Identify the installed Framemaker version
    Open Adobe Framemaker, go to Help > About Adobe Framemaker to display the full version number (for example, 2019.0.8 or 2020.0.4), or check the registry value DisplayVersion under the product's uninstall key
    Affected if A version number is displayed showing the installed release
  3. Compare version against affected 2019 range
    If the version begins with 2019 (such as 2019.0.x), verify whether the minor version number (x) is 8 or lower; versions 2019.0.0 through 2019.0.8 are affected
    Affected if Version is 2019.0.x where x is 0 through 8 inclusive
  4. Compare version against affected 2020 range
    If the version begins with 2020 (such as 2020.0.x), verify whether the minor version number (x) is 4 or lower; versions 2020.0.0 through 2020.0.4 are affected
    Affected if Version is 2020.0.x where x is 0 through 4 inclusive

The environment is affected if Adobe Framemaker is installed and the identified version falls within 2019.0.0-2019.0.8 or 2020.0.0-2020.0.4, making the file parsing component vulnerable to the out-of-bounds write when opening specially crafted 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 a release after 2020.0.4
Interim mitigation

Update Adobe Framemaker to the latest patched version; avoid opening untrusted or unexpected files from unknown sources.

Recommended fix High confidence

Framemaker 2019.0.9 or later; Framemaker 2020.0.5 or later (or latest available version)

  1. 1. Identify the currently installed Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. 2. If running Framemaker 2019.x (versions 2019.0 through 2019.0.8), download and install Framemaker 2019 Update 9 or later from Adobe's official download page
  3. 3. If running Framemaker 2020.x (versions 2020.0 through 2020.0.4), download and install Framemaker 2020 Update 5 or later from Adobe's official download page
  4. 4. Alternatively, upgrade to the latest available Framemaker version (2022 or later) which includes all security patches
  5. 5. After installation, verify the new version by checking Help > About Adobe Framemaker
  6. 6. Ensure all users are informed not to open untrusted .fm or other document files from unknown sources
Caveat Standard upgrade considerations apply - test critical documents and templates with the new version before widespread deployment

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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