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

> Heap bounds overwrite in Sane test utility allows code execution if attacker-controlled config is used, though exploitation is disputed.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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:** 27 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-46052, GHSA-86vw-c532-f7g7

## What is CVE-2023-46052?

CVE-2023-46052 is a high-severity memory corruption vulnerability in n/a, published on 27 Mar 2024. 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

Sane 1.2.1 heap bounds overwrite in init_options() from backend/test.c via a long init_mode string in a configuration file. NOTE: this is disputed because there is no expectation that test.c code should be executed with an attacker-controlled configuration file.

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

It affects 1 product.


Products: Sane-Project Sane Backends.

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

Apply the vendor's patch.

## Is CVE-2023-46052 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-46047](https://insights.sbomify.com/CVE-2023-46047/): Code injection in n/a (high 7.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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