# CVE-2023-43907: Memory corruption in n/a

> A global buffer overflow in OptiPNG allows attackers to execute arbitrary code or cause denial of service via crafted GIF files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Oct 2023
- **Updated:** 23 Sep 2024
- **Also known as:** AZL-36971, AZL-37153, DEBIAN-CVE-2023-43907, GHSA-xwf2-9m25-2hpf, MGASA-2023-0333, OESA-2023-1873, UBUNTU-CVE-2023-43907, openSUSE-SU-2023:0388-1, openSUSE-SU-2024:13415-1

## What is CVE-2023-43907?

CVE-2023-43907 is a high-severity memory corruption vulnerability in n/a, published on 1 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

OptiPNG v0.7.7 was discovered to contain a global buffer overflow via the 'buffer' variable at gifread.c.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `optipng` | SUSE:Package Hub 15 SP4 | All versions | 0.7.8-bp154.3.5.1 |
| `optipng` | openSUSE:Leap 15.4 | All versions | 0.7.8-bp154.3.5.1 |
| `optipng` | openSUSE:Tumbleweed | All versions | 0.7.8-1.1 |

Products: Optipng Project Optipng.

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

Apply the vendor's patch.

## Is CVE-2023-43907 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-16938](https://insights.sbomify.com/CVE-2017-16938/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43907 is a high-severity memory corruption vulnerability in n/a, published on 1 Oct 2023. It can only be exploited from the same machine or local network, 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-43907 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-43907/ (Markdown: https://insights.sbomify.com/CVE-2023-43907/index.md)
```

## Sources

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

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