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

> Remote attackers can execute arbitrary code via a crafted erofs filesystem image due to a heap buffer overflow in erofs-utils.

- **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 Jun 2023
- **Updated:** 9 Jan 2025
- **Also known as:** DEBIAN-CVE-2023-33551, GHSA-2f78-w4rr-cmhf, UBUNTU-CVE-2023-33551, openSUSE-SU-2024:13318-1

## What is CVE-2023-33551?

CVE-2023-33551 is a high-severity memory corruption vulnerability in n/a, published on 1 Jun 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

Heap Buffer Overflow in the erofsfsck_dirent_iter function in fsck/main.c in erofs-utils v1.6 allows remote attackers to execute arbitrary code via a crafted erofs filesystem image.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `erofs-utils` | openSUSE:Tumbleweed | All versions | 1.7-1.1 |

Products: Erofs-Utils Project Erofs-Utils.

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

Apply the vendor's patch.

## Is CVE-2023-33551 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33551 is a high-severity memory corruption vulnerability in n/a, published on 1 Jun 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-33551 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-33551/ (Markdown: https://insights.sbomify.com/CVE-2023-33551/index.md)
```

## Sources

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

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