dbcve.org
Debian LinuxOperating system · Debian

CVE-2023-32307

HIGH · 7.5 CVSS v3.1 Published 2023-05-26
Fix available
A fix is available. Upgrade to 1.13.15 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Sofia-SIP library contains heap overflow and integer overflow vulnerabilities in STUN packet parsing functions stun_parse_attr_error_code and stun_parse_attr_uint32 due to missing attributes length validation. Attackers can craft malicious STUN packets with insufficient length checks, causing out-of-bounds reads, memory corruption, crashes, or excessive memory consumption.

MitigationUpgrade Sofia-SIP to version 1.13.15 or later to obtain the patched code with proper attribute length validation. If upgrade is not immediately feasible, implement input validation filters for STUN packets at network boundaries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 10.0
Sofia SipApplication
Affected:< 1.13.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Sofia-SIP installation
    Search for Sofia-SIP libraries in common locations: /usr/lib/libsofia-sip-ua.so*, /usr/lib64/libsofia-sip-ua.so*, or use package manager commands like 'dpkg -l | grep sofia-sip' (Debian) or 'rpm -qa | grep sofia-sip' (RHEL-based). Also check for linked binaries using 'ldconfig -p | grep sofia' or 'find /usr -name "*sofia*"'
    Affected if Sofia-SIP library is present on the system
  2. Determine installed Sofia-SIP version
    If using Debian: run 'dpkg -l libsofia-sip-ua0' to get the version. If a binary is found: run 'strings <path_to_lib> | grep -i "sofia.*sip"' or check the shared library filename which may contain the version. Compare against the affected range: versions before 1.13.15 are vulnerable
    Affected if Installed version is before 1.13.15 or version cannot be determined
  3. Verify STUN protocol processing is enabled
    Search configuration files and application logs for STUN configuration: look for 'stun' keyword in config files (e.g., /etc/, /opt/, application config directories), check running processes for STUN-related parameters using 'ps aux | grep -i stun', and review network service configurations for port 3478 (STUN default port)
    Affected if STUN processing is actively enabled or configured in any application using Sofia-SIP
  4. Inspect STUN packet handling code paths
    If source code is available: search for calls to 'stun_parse_attr_error_code' and 'stun_parse_attr_uint32' functions. If binary only: use 'nm -D <libsofia> | grep stun_parse_attr' or 'objdump -T <libsofia> | grep stun_parse_attr' to confirm these functions are exported and linked
    Affected if The vulnerable parsing functions stun_parse_attr_error_code or stun_parse_attr_uint32 are present and used

A system is affected if Sofia-SIP version below 1.13.15 is installed AND STUN protocol processing is enabled, as the vulnerability requires both the unpatched library and active STUN packet handling to be exploitable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.13.15 or later
Fixed in 1.13.15
Interim mitigation

Upgrade Sofia-SIP to version 1.13.15 or later to obtain the patched code with proper attribute length validation. If upgrade is not immediately feasible, implement input validation filters for STUN packets at network boundaries.

Recommended fix High confidence

1.13.15

  1. Update the package repository: apt-get update
  2. Upgrade Sofia-SIP library to version 1.13.15 or later: apt-get install libsofia-sip-ua0 (or apt-get upgrade libsofia-sip-ua0)
  3. Verify the installed version matches 1.13.15 or higher: dpkg -l | grep sofia-sip
  4. If using Sofia-SIP in any running services, restart them to load the updated library

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32307 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data