Security readout for executives and security teams
Plain-English summary
Xpdf 4.04 has a reported stack overflow that can crash the application when a user interaction reaches the vulnerable code path. The documented impact is availability loss, not data theft or privilege escalation.
Executive priority
Treat as a moderate availability risk. Prioritize environments where PDF processing is business-critical or exposed to untrusted files, but do not treat it as confirmed internet-exploited ransomware-grade risk from the supplied evidence.
Technical view
CVE-2022-43295 is a CWE-121 stack-based buffer overflow in FileStream::copy() at xpdf/Stream.cc:795 in Xpdf 4.04. The CVSS 3.1 score is 5.5 with local attack vector, low complexity, no privileges, required user interaction, and high availability impact.
Likely exposure
Exposure is most likely where Xpdf 4.04 is installed directly or bundled into document viewing or PDF-processing workflows. The source bundle does not provide CPEs or a broader affected-version range.
Exploitation context
The CVSS vector indicates local access and user interaction are required. The bundle does not show active exploitation, and this CVE is not listed as KEV. Public details are sparse.
Researcher notes
The record identifies the vulnerable function and line but provides limited reproduction, affected-version, and remediation detail. Avoid expanding scope beyond Xpdf 4.04 unless vendor or CVE updates confirm it.
Mitigation direction
- Inventory Xpdf installations and embedded uses of Xpdf libraries.
- Check Xpdf vendor guidance for fixed versions or supported mitigations.
- Limit handling of untrusted PDFs on systems using Xpdf 4.04.
- Run document processing with least privilege and isolation where practical.
Validation and detection
- Confirm whether Xpdf 4.04 is present on endpoints or servers.
- Check software bills of materials for bundled Xpdf components.
- Review PDF-processing workflows that invoke Xpdf locally.
- Track vendor forum or CVE updates for patch confirmation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-43295 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://forum.xpdfreader.com/viewtopic.php?t=42360CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
