# CVE-2023-25076: Memory corruption in SNIProxy

> A buffer overflow in SNIProxy allows remote attackers to execute arbitrary code via crafted HTTP or TLS packets.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2023
- **Updated:** 5 Mar 2025
- **Also known as:** DEBIAN-CVE-2023-25076, DLA-3406-1, DSA-5413-1, GHSA-fhgm-rvpq-xwx9, MGASA-2023-0178, UBUNTU-CVE-2023-25076, USN-6148-1

## What is CVE-2023-25076?

CVE-2023-25076 is a critical memory corruption vulnerability in SNIProxy, published on 30 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow vulnerability exists in the handling of wildcard backend hosts of SNIProxy 0.6.0-2 and the master branch (commit: 822bb80df9b7b345cc9eba55df74a07b498819ba). A specially crafted HTTP or TLS packet can lead to arbitrary code execution. An attacker could send a malicious packet to trigger this vulnerability.

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

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

It affects 1 product.


Products: Sniproxy Project Sniproxy.

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

Apply the vendor's patch.

## Is CVE-2023-25076 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-25076 is a critical memory corruption vulnerability in SNIProxy, published on 30 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25076 exists.

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

## Sources

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

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