# CVE-2023-32307: heap-over-flow and integer-overflow in sofia-sip

> Attackers can trigger heap overflows and integer overflows in Sofia-SIP via crafted STUN packets, causing crashes or potential code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2023
- **Updated:** 13 Feb 2025
- **Also known as:** DEBIAN-CVE-2023-32307, DLA-3441-1, DSA-5431-1, GHSA-rm4c-ccvf-ff9c, MGASA-2023-0209, UBUNTU-CVE-2023-32307, USN-6448-1

## What is CVE-2023-32307?

CVE-2023-32307 is a high-severity vulnerability in Debian Debian Linux, published on 26 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sofia-SIP is an open-source SIP User-Agent library, compliant with the IETF RFC3261 specification.
Referring to [GHSA-8599-x7rq-fr54](https://github.com/freeswitch/sofia-sip/security/advisories/GHSA-8599-x7rq-fr54), several other potential heap-over-flow and integer-overflow in stun_parse_attr_error_code and stun_parse_attr_uint32 were found because the lack of attributes length check when Sofia-SIP handles STUN packets. The previous patch of [GHSA-8599-x7rq-fr54](https://github.com/freeswitch/sofia-sip/security/advisories/GHSA-8599-x7rq-fr54) fixed the vulnerability when attr_type did not match the enum value, but there are also vulnerabilities in the handling of other valid cases. The OOB read and integer-overflow made by attacker may lead to crash, high consumption of memory or even other more serious consequences. These issue have been addressed in version 1.13.15. Users are advised to upgrade.

Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow)

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

It affects 2 products.


Products: Debian Debian Linux, Signalwire Sofia-Sip.

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

Upgrade to a fixed version.

## Is CVE-2023-32307 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32307 is a high-severity vulnerability in Debian Debian Linux, published on 26 May 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-32307 exists.

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

## Sources

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

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