CVE-2022-28830
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 · uneditedAdobe Framemaker versions 2029u8 (and earlier) and 2020u4 (and earlier) 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 confidenceAdobe Framemaker contains an out-of-bounds read vulnerability where parsing a specially crafted malicious file allows reading memory beyond allocated buffer boundaries. This information disclosure can leak sensitive data and assist in bypassing ASLR security mitigations. Exploitation requires user interaction—the victim must open the malicious file.
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>= 2019, <= 2019.0.8>= 2020, <= 2020.0.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Framemaker is installedOn Windows, open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ and look for entries named 'Adobe Framemaker' or check the program files directory (C:\Program Files\Adobe\Adobe FrameMaker*). On macOS, check /Applications for Adobe Framemaker.app or run 'system_profiler SPApplicationsDataType' in Terminal.Affected if No Adobe Framemaker installation is found - the system is not affected by this CVE.
-
Determine installed Framemaker version numberOn Windows, locate the Adobe Framemaker registry entry and read the 'DisplayVersion' value (REG_SZ), or right-click the executable in Program Files and select Properties > Details to view File Version. On macOS, right-click Adobe Framemaker.app > Get Info to see the version number.Affected if The version cannot be determined - further investigation may be required.
-
Compare version against affected rangesReview the detected version number and compare it to the affected ranges: 2019.0 through 2019.0.8 (any 2019.x version up to and including 2019.0.8) and 2020.0 through 2020.0.4 (any 2020.x version up to and including 2020.0.4).Affected if The installed version falls within 2019.0 to 2019.0.8 OR 2020.0 to 2020.0.4 - the environment is affected by this vulnerability.
-
Assess user interaction riskReview whether users have the ability to open document files (.fm, .mif, or other Framemaker formats) from external or untrusted sources. Check recent file access logs or interview users about file opening habits.Affected if Users routinely open Framemaker documents from email attachments, downloads, or other untrusted sources - exploitation becomes feasible.
The system is affected if Adobe Framemaker versions 2019.0 through 2019.0.8 or 2020.0 through 2020.0.4 are installed AND users can open potentially malicious document files.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate Adobe Framemaker to a patched version beyond 2029u8 and 2020u4. Additionally, train users to avoid opening files from untrusted sources to reduce exploitation risk.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-28830 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28830 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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