# CVE-2022-0856: Denial of service in libcaca

> A divide-by-zero error in libcaca's img2txt tool allows remote attackers to cause a denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-0856, ECHO-d40e-0bf5-74be, GHSA-p2c9-9qhg-mq4q, MGASA-2022-0172, SUSE-SU-2022:1476-1, SUSE-SU-2022:1508-1, UBUNTU-CVE-2022-0856, USN-7943-1, openSUSE-SU-2024:12029-1

## What is CVE-2022-0856?

CVE-2022-0856 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 8 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

libcaca is affected by a Divide By Zero issue via img2txt, which allows a remote malicious user to cause a Denial of Service

Weakness: CWE-369 (Divide By Zero)

## Which versions are affected by CVE-2022-0856?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libcaca` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 0.99.beta19.git20171003-150200.11.6.1 |
| `libcaca` | SUSE:Linux Enterprise Real Time 15 SP2 | All versions | 0.99.beta19.git20171003-150200.11.6.1 |
| `libcaca` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 0.99.beta18-14.9.1 |
| `libcaca` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 0.99.beta18-14.9.1 |
| `libcaca` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 0.99.beta18-14.9.1 |
| `libcaca` | openSUSE:Leap 15.3 | All versions | 0.99.beta19.git20171003-150200.11.6.1 |
| `libcaca` | openSUSE:Leap 15.4 | All versions | 0.99.beta19.git20171003-150200.11.6.1 |

Products: Fedoraproject Fedora, Libcaca Project Libcaca.

## How do I fix CVE-2022-0856?

Apply the vendor's patch.

## Is CVE-2022-0856 being exploited?

There is no known exploitation of CVE-2022-0856 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0856 and fix it if it is affected.

What it is: CVE-2022-0856 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 8 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-0856 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0856/ (Markdown: https://insights.sbomify.com/CVE-2022-0856/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0856
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0856
- OSV: https://osv.dev/vulnerability/CVE-2022-0856

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0856/
Summaries are generated and may contain mistakes; the official description above is the record.