CVE-2022-42339
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 Acrobat Reader versions 22.002.20212 (and earlier) and 20.005.30381 (and earlier) are affected by a Stack-based Buffer Overflow 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 confidenceA stack-based buffer overflow vulnerability exists in Adobe Acrobat Reader versions 22.002.20212 and earlier, and 20.005.30381 and earlier. Successful exploitation allows arbitrary code execution in the context of the current user, but requires the victim to open a malicious PDF 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>= 15.008.20082, < 22.003.20258>= 15.008.20082, < 22.003.20258>= 20.001.30005, < 20.005.30407>= 20.001.30005, < 20.005.30407CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Adobe Acrobat or Reader is installedCheck the installed programs on Windows (Control Panel > Programs and Features, or run `Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion` in PowerShell), or on macOS check /Applications for Adobe Acrobat or Adobe Reader applicationsAffected if Adobe Acrobat Dc, Adobe Acrobat Reader Dc, Adobe Acrobat, or Adobe Acrobat Reader is present on the system
-
Determine the exact installed versionRight-click the Adobe application in the installed programs list to view the version, or open the application and go to Help > About Adobe Acrobat/Reader to display the full version number (e.g., 22.002.20212 or 20.005.30381)Affected if The displayed version matches one of the affected product lines and falls within the vulnerable ranges
-
Compare against affected version rangesFor Adobe Acrobat Dc or Adobe Acrobat Reader Dc: check if version is >= 15.008.20082 and < 22.003.20258. For Adobe Acrobat or Adobe Acrobat Reader: check if version is >= 20.001.30005 and < 20.005.30407Affected if The installed version falls within any of these ranges, indicating the system is vulnerable to CVE-2022-42339
-
Verify the PDF handling component is in useThe vulnerability is triggered when opening a malicious PDF file. Check if the user frequently opens PDF files from untrusted sources or if Adobe Acrobat/Reader is set as the default PDF handlerAffected if Adobe Acrobat or Reader is the default PDF viewer and is used to open PDF files from various sources, increasing the likelihood of exploitation
A system is affected if Adobe Acrobat Dc, Adobe Acrobat Reader Dc, Adobe Acrobat, or Adobe Acrobat Reader is installed with a version between the minimum and maximum affected numbers listed in the CVE, and the user opens PDF 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.
dbcve · scoped20.005.3040722.003.20258
Update Adobe Acrobat Reader to the latest version (newer than 22.002.20212 or 20.005.30381) and avoid opening untrusted PDF files from unknown sources.
Adobe Acrobat/Reader DC: upgrade to 22.003.20258 or later; Adobe Acrobat/Reader (2020): upgrade to 20.005.30407 or later
- 1. Open Adobe Acrobat Reader or Adobe Acrobat on your system
- 2. Navigate to Help > Check for Updates (or use the Help menu)
- 3. Allow the application to check for available updates
- 4. If updates are available, review the update details to confirm version 22.003.20258 or later (for DC products) or 20.005.30407 or later (for standard Acrobat/Reader)
- 5. Download and install the recommended update
- 6. Restart the application after installation
- 7. Verify the installed version matches or exceeds the minimum fixed version (Help > About Adobe Acrobat/Reader)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42339 — 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-42339 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