CVE-2026-45103

OpenSIPS: SIP Message Smuggling via TCP Content-Length Integer Overflow

Published Aug 4, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
OpenSIPS is a Session Initiation Protocol (SIP) server implementation. In versions prior to 3.6.6 and 4.0.0-rc1, the TCP message framing layer parses the Content-Length header using unsigned int arithmetic with no overflow check. When an attacker sends a Content-Length value that overflows unsigned int (e.g., 4294967296), the framing layer computes a wrapped-around value (e.g., 0) and splits the TCP stream at the wrong boundary, causing the body of the first SIP message to be processed as a separate message and enabling SIP message smuggling. Because Content-Length is parsed in the transport layer before authentication, an unauthenticated, network-based attacker can smuggle arbitrary SIP messages over any TCP-based transport (proto_tcp, proto_tls, proto_ws, proto_wss) on any instance with TCP enabled, with no routing-script preconditions. This allows smuggled messages to bypass front-end SBC/proxy security policies, inherit the connection's authentication context, and evade rate limiting. This issue has been fixed in versions 3.6.6 and 4.0.0-rc1.

Analysis

AI-generated

Technical impact

A TCP Content-Length integer overflow in OpenSIPS allows a network attacker to send a header value that wraps the unsigned integer, causing the server to split the stream incorrectly. The body of the first SIP message is treated as a second, separate message, enabling smuggling of arbitrary SIP commands. Because the vulnerable parsing occurs before authentication, the attacker can use any TCP‑based transport (proto_tcp, proto_tls, proto_ws, proto_wss) on a server with TCP enabled, bypassing front‑end SBC or proxy security policies, inheriting the connection’s authentication context, and evading rate limiting.

Affected Systems

The issue affects OpenSIPS servers running any version earlier than 3.6.6 or before the 4.0.0‑rc1 release. Both the community editions (OpenSIPS:opensips) and any deployments that enable TCP‑based transports are vulnerable, regardless of platform or operating system.

Risk and Exploitability

The vulnerability has a CVSS score of 7.5, indicating moderate‑high risk, and no EPSS score is available. It is not listed in the CISA KEV catalog. An unauthenticated attacker with network access can exploit the flaw by sending a crafted SIP message with an overlarge Content‑Length header. This attack is straightforward and does not require any authentication or special privileges, making it feasible for adversaries to inject malicious SIP commands that could compromise subsequent communication channels or subvert access controls.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade OpenSIPS to version 3.6.6 or later (or 4.0.0‑rc1 or newer) to apply the fixed integer overflow check.
  • If upgrading is not immediately possible, apply the patch commits 4d23613b or 5f103eff to the source distribution, rebuild, and redeploy the service.
  • As a temporary measure, disable or restrict TCP, TLS, WS, and WSS transports for unauthenticated clients, or enforce firewall rules that block unsolicited inbound SIP traffic until the patch is applied.

Generated by OpenCVE AI on August 4, 2026 at 23:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Opensips
Opensips opensips
Vendors & Products Opensips
Opensips opensips
Type Values Removed Values Added
Description OpenSIPS is a Session Initiation Protocol (SIP) server implementation. In versions prior to 3.6.6 and 4.0.0-rc1, the TCP message framing layer parses the Content-Length header using unsigned int arithmetic with no overflow check. When an attacker sends a Content-Length value that overflows unsigned int (e.g., 4294967296), the framing layer computes a wrapped-around value (e.g., 0) and splits the TCP stream at the wrong boundary, causing the body of the first SIP message to be processed as a separate message and enabling SIP message smuggling. Because Content-Length is parsed in the transport layer before authentication, an unauthenticated, network-based attacker can smuggle arbitrary SIP messages over any TCP-based transport (proto_tcp, proto_tls, proto_ws, proto_wss) on any instance with TCP enabled, with no routing-script preconditions. This allows smuggled messages to bypass front-end SBC/proxy security policies, inherit the connection's authentication context, and evade rate limiting. This issue has been fixed in versions 3.6.6 and 4.0.0-rc1.
Title OpenSIPS: SIP Message Smuggling via TCP Content-Length Integer Overflow
Weaknesses CWE-190
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-190

    Integer Overflow or Wraparound

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 5, 2026, 5:55 PM
Reserved
May 8, 2026, 7:27 PM
Status
Awaiting Analysis
Published
Aug 4, 2026, 10:17 PM
Modified
Sep 8, 2026, 8:41 PM