CVE-2022-24107

Xpdf prior to 4.04 lacked an integer overflow check in JPXStream.cc.

Published: 2022-08-30 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-24107 is rated Low Risk (39.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.08%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-24107

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.05% 0.08% +0.03%
2 2025-11-18 0.05% 0.05% -0.00%
3 2023-03-07 — 0.05% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-24107

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2022-24107

OS Trackers for CVE-2022-24107

vendor priority summary link
alpine high CVE-2022-24107: 1 source package rows (xpdf); 5 state rows across 5 repos (3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2022-24107
debian unimportant CVE-2022-24107 unimportant priority: Debian including 1 source packages (xpdf), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-24107
gentoo normal CVE-2022-24107: 1 GLSA(s) (202405-18), 1 atom(s) (app-text/xpdf); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-24107
suse medium CVE-2022-24107 severity moderate: SUSE including 12 source package names (libpoppler-cpp0, libpoppler-devel, …), 164 product×package rows across 29 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 7, … (29 product lines)): Known Not Affected 164. https://www.suse.com/security/cve/CVE-2022-24107/
ubuntu medium CVE-2022-24107 medium priority: Ubuntu including 4 source packages (emscripten, ipe, texlive-bin, xpdf), 52 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 17, needs-triage 15, not-affected 13, DNE 4, released 3. https://ubuntu.com/security/CVE-2022-24107

Affected software / configurations for CVE-2022-24107

Vendor Product Version Raw CPE
glyphandcog xpdfreader < 4.04 cpe:2.3:a:glyphandcog:xpdfreader:*:*:*:*:*:*:*:*

References for CVE-2022-24107

cvelogic Threat Intelligence