CVE-2022-29977

Exp

There is an assertion failure error in stbi__jpeg_huff_decode, stb_image.h:1894 in libsixel img2sixel 1.8.6. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted JPEG file.

Published: 2022-05-11 Last update: 2026-04-24 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-29977 is rated High Exploit Risk (65/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.56%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2022-29977

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

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

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 2026-01-17 0.30% 0.56% +0.26%
2 2025-05-20 0.68% 0.30% -0.38%
3 2025-05-13 — 0.68% —

Full EPSS history (6 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2022-29977

OS Trackers for CVE-2022-29977

vendor priority summary link
debian not yet assigned CVE-2022-29977 not yet assigned priority: Debian including 1 source packages (libsixel), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2022-29977
ubuntu medium CVE-2022-29977 medium priority: Ubuntu including 1 source packages (libsixel), 13 status rows across 13 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, upstream, xenial): needs-triage 7, ignored 6. https://ubuntu.com/security/CVE-2022-29977

Affected software / configurations for CVE-2022-29977

Vendor Product Version Raw CPE
saitoha libsixel 1.8.6 cpe:2.3:a:saitoha:libsixel:1.8.6:*:*:*:*:*:*:*

References for CVE-2022-29977

URL Tags
https://github.com/saitoha/libsixel/issues/165 Exploit Issue Tracking Third Party Advisory
cvelogic Threat Intelligence