libcaca is affected by a Divide By Zero issue via img2txt, which allows a remote malicious user to cause a Denial of Service
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.7% (FIRST EPSS); higher than 86% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: libcaca (Debian:14) 0.99.beta20-8; libcaca (SUSE:Linux Enterprise Module for Basesystem 15 SP3) 0.99.beta19.git20171003-150200.11.6.1; libcaca (SUSE:Linux Enterprise Software Development Kit 12 SP5) 0.99.beta18-14.9.1.
Low priority for now. Upgrade to libcaca (Debian:14) 0.99.beta20-8; libcaca (SUSE:Linux Enterprise Module for Basesystem 15 SP3) 0.99.beta19.git20171003-150200.11.6.1; libcaca (SUSE:Linux Enterprise Software Development Kit 12 SP5) 0.99.beta18-14.9.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Mar 10, 2022
- Updated
- Jun 17, 2026
- EPSS
- 2.7% · 86th percentile
- CWE
- CWE-369
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libcaca project | libcaca | cpe:2.3:a:libcaca_project:libcaca |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora37
- fedoraproject fedora38
- libcaca project libcaca0.99
Versions reported by the vendor
Affected version ranges reported by the assigning authority (fedora). Independent of NVD's CPE analysis and usually ahead of it.
n/a libcaca
- libcaca - v0.99.beta20affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libcaca | from 0 | — |
| Debian:14 | libcaca | before 0.99.beta20-8 | 0.99.beta20-8 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | libcaca | before 0.99.beta19.git20171003-150200.11.6.1 | 0.99.beta19.git20171003-150200.11.6.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | libcaca | before 0.99.beta19.git20171003-150200.11.6.1 | 0.99.beta19.git20171003-150200.11.6.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | libcaca | before 0.99.beta18-14.9.1 | 0.99.beta18-14.9.1 |
Same product
libcaca project: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-20549There is an illegal WRITE memory access at caca/file.c (function caca_file_read) in libcaca 0.99.beta19.36Monitor
- CVE-2018-20548There is an illegal WRITE memory access at common-image.c (function load_image) in libcaca 0.99.beta19 for 1bpp data.36Monitor
- CVE-2018-20545There is an illegal WRITE memory access at common-image.c (function load_image) in libcaca 0.99.beta19 for 4bpp data.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-3410Feb 23, 2021 · A flaw was found in libcaca v0.99.beta19.31Monitor
- ← EarlierCVE-2021-30498May 26, 2021 · A flaw was found in libcaca.31Monitor
- ← EarlierCVE-2021-30499May 26, 2021 · A flaw was found in libcaca.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libcaca | 0.99.beta20-8 · Debian:14 | Package registry (OSV) |
| opensuse:libcaca | 0.99.beta19.git20171003-150200.11.6.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| suse:libcaca | 0.99.beta19.git20171003-150200.11.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-369 · Divide By ZeroCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.