# CVE-2023-37769: Integer overflow in n/a

> A floating-point exception in the Pixman library's combine_inner function can 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:** 17 Jul 2023
- **Updated:** 30 Oct 2024
- **Also known as:** AZL-28509, DEBIAN-CVE-2023-37769, GHSA-jhr6-5fqf-6p96, MINI-hw7p-78c2-p87v, UBUNTU-CVE-2023-37769

## What is CVE-2023-37769?

CVE-2023-37769 is a medium-severity vulnerability in n/a, published on 17 Jul 2023. 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

stress-test master commit e4c878 was discovered to contain a FPE vulnerability via the component combine_inner at /pixman-combine-float.c.

Weakness: CWE-369 (Divide By Zero)

## Which versions are affected by CVE-2023-37769?

It affects 1 product.


Products: Pixman Pixman.

## How do I fix CVE-2023-37769?

Apply the vendor's patch.

## Is CVE-2023-37769 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37769 exists.

## Other vulnerabilities in n/a

- [CVE-2015-5297](https://insights.sbomify.com/CVE-2015-5297/): Integer overflow in pixman (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37769 and fix it if it is affected.

What it is: CVE-2023-37769 is a medium-severity vulnerability in n/a, published on 17 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37769 exists.

Affected product: n/a. 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-2023-37769/ (Markdown: https://insights.sbomify.com/CVE-2023-37769/index.md)
```

## Sources

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

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