CVE-2026-54632: SIPSorcery Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-28gm-jrmw-xx93
CVSS 7.5
CWE-755 CWE-20
Published
Advisory Summary

CVE-2026-54632 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-755: Improper Handling of Exceptional Conditions) affecting SIPSorcery libraries in the NuGet ecosystem. The issue involves malformed udp packet on the rtp/ice socket can remotely terminate a media session (dos). Remediation is available by upgrading affected packages to version 10.0.9.

CVE-2026-54632 at a Glance

CVE Identifier CVE-2026-54632
GHSA Identifier GHSA-28gm-jrmw-xx93
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-755: Improper Handling of Exceptional Conditions
Affected Product SIPSorcery
Package Ecosystem NuGet
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-54632

To remediate this vulnerability, upgrade all affected SIPSorcery dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

SIPSorcery fixed: 10.0.9
Upgrade SIPSorcery to 10.0.9
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for SIPSorcery

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-54632, inspect your project dependencies for SIPSorcery:

inspect dependencies for SIPSorcery

Analyze the terminal output to locate any version of SIPSorcery in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 10.0.9), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-755: Improper Handling of Exceptional Conditions, where the product does not handle or incorrectly handles an exceptional condition. In SIPSorcery, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A single malformed inbound UDP packet on the RTP/ICE socket can remotely terminate an active RTP or WebRTC media session. The packet receive handler indexes packet (and STUN attribute) bytes without sufficient length checks and throws, and the UDP receive loop converted any such exception into a channel `Close` rather than dropping the packet. One small, unauthenticated packet therefore ends the media session. This is reachable during ICE connectivity checks — before the DTLS handshake and before any STUN `MESSAGE-INTEGRITY` verification. Because the RTP/ICE port is shared/advertised in the ICE candidates, a peer or on-path attacker can reach it (exposure is lower for a blind off-path attacker that must first learn the ephemeral port). Impact is availability only — no loss of confidentiality or integrity. ### Affected versions NuGet package `SIPSorcery` `<= 10.0.8`. ### Patches Fixed in `10.0.9`. ### Root cause Two issues combine: 1. **Unchecked indexing of untrusted bytes.** - `RTPChannel.OnRTPPacketReceived` read `packet[1]` after only checking the packet was non-empty, so a 1-byte packet threw `IndexOutOfRangeException`. - `STUNAttribute.ParseMessageAttributes` passed a `null`/short value to the typed attribute parsers, and `STUNXORAddressAttribute` (and the non-XOR `STUNAddressAttribute`) then read `attributeValue[1]`, `AsSpan(2)` and `AsSpan(4)` with no length check. A STUN message carrying an `XOR-MAPPED-ADDRESS`, `XOR-PEER-ADDRESS` or `XOR-RELAYED-ADDRESS` attribute of length 0–7 threw (`NullReferenceException` for length 0, `IndexOutOfRangeException`/`ArgumentOutOfRangeException` for 1–7). 2. **The UDP receive loop closed the channel on any exception.** The catch-all in `UdpReceiver.EndReceiveFrom` called `Close()`, tearing down the channel, instead of dropping the offending packet and continuing. This was systemic: any unhandled exception anywhere in the packet pipeline (STUN, RTP, RTCP, DTLS demux, SRTP, TURN) became a channel teardown. ### Fix - `UdpReceiver.EndReceiveFrom`: a non-socket exception now logs and drops the single packet and re-arms the receive loop (matching the existing `SIPUDPChannel` behaviour), instead of closing the channel. Genuine socket failures continue to be handled separately. - `RTPChannel.OnRTPPacketReceived`: requires a minimum packet length (`RTPHeader.MIN_HEADER_LEN`) before indexing the discriminator bytes. - STUN parsing: `ParseMessageAttributes` validates each attribute value length and skips malformed/truncated attributes; the XOR/address attribute constructors validate length defensively; `ParseSTUNMessage` no longer dereferences a null attribute list. Regression tests were added covering the 1-byte packet (channel stays open and remains usable), short/zero-length XOR address attributes (0–7 bytes), and truncated STUN messages. ### Workarounds None within the library short of upgrading. Restricting the RTP/ICE port to known peers at the network layer reduces exposure but does not eliminate it, since a negotiating peer can still trigger the condition. ### Credit Responsibly reported by Lokhesh Ujhoodha.

CVE-2026-54632 Affected SIPSorcery Versions

1 component(s)
Fixed Versions:
10.0.9
Product / Package Ecosystem Affected Versions Fixed Version
SIPSorcery
NuGet
< 10.0.9
10.0.9

References

Frequently Asked Questions

What is CVE-2026-54632?
CVE-2026-54632 is a security vulnerability in SIPSorcery involving Malformed UDP packet on the RTP/ICE socket can remotely terminate a media session (DoS) under CWE-755: Improper Handling of Exceptional Conditions.
Which SIPSorcery versions are affected?
Affected versions include releases prior to 10.0.9 across affected packages: SIPSorcery.
What version fixes CVE-2026-54632?
Upgrading to 10.0.9 (or the latest patched release for your respective branch) resolves the vulnerability.
Is SIPSorcery affected?
Yes, SIPSorcery is affected in releases prior to 10.0.9. Upgrade your dependency to 10.0.9 or later.
What is the CVSS score of CVE-2026-54632?
CVE-2026-54632 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-54632?
CVE-2026-54632 is classified under CWE-755: Improper Handling of Exceptional Conditions (The product does not handle or incorrectly handles an exceptional condition.).
How can I check NuGet dependencies for CVE-2026-54632?
Run the dependency tree command: 'inspect dependencies for SIPSorcery'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-28gm-jrmw-xx93",
  "modified" : "2026-07-28T17:01:19Z",
  "published" : "2026-07-28T17:01:19Z",
  "aliases" : [ "CVE-2026-54632" ],
  "summary" : "SIPSorcery: Malformed UDP packet on the RTP/ICE socket can remotely terminate a media session (DoS)",
  "details" : "### Impact\n\nA single malformed inbound UDP packet on the RTP/ICE socket can remotely terminate an active RTP or WebRTC media session. The packet receive handler indexes packet (and STUN attribute) bytes without sufficient length checks and throws, and the UDP receive loop converted any such exception into a channel `Close` rather than dropping the packet. One small, unauthenticated packet therefore ends the media session.\n\nThis is reachable during ICE connectivity checks — before the DTLS handshake and before any STUN `MESSAGE-INTEGRITY` verification. Because the RTP/ICE port is shared/advertised in the ICE candidates, a peer or on-path attacker can reach it (exposure is lower for a blind off-path attacker that must first learn the ephemeral port). Impact is availability only — no loss of confidentiality or integrity.\n\n### Affected versions\n\nNuGet package `SIPSorcery` `<= 10.0.8`.\n\n### Patches\n\nFixed in `10.0.9`.\n\n### Root cause\n\nTwo issues combine:\n\n1. **Unchecked indexing of untrusted bytes.**\n   - `RTPChannel.OnRTPPacketReceived` read `packet[1]` after only checking the packet was non-empty, so a 1-byte packet threw `IndexOutOfRangeException`.\n   - `STUNAttribute.ParseMessageAttributes` passed a `null`/short value to the typed attribute parsers, and `STUNXORAddressAttribute` (and the non-XOR `STUNAddressAttribute`) then read `attributeValue[1]`, `AsSpan(2)` and `AsSpan(4)` with no length check. A STUN message carrying an `XOR-MAPPED-ADDRESS`, `XOR-PEER-ADDRESS` or `XOR-RELAYED-ADDRESS` attribute of length 0–7 threw (`NullReferenceException` for length 0, `IndexOutOfRangeException`/`ArgumentOutOfRangeException` for 1–7).\n\n2. **The UDP receive loop closed the channel on any exception.** The catch-all in `UdpReceiver.EndReceiveFrom` called `Close()`, tearing down the channel, instead of dropping the offending packet and continuing. This was systemic: any unhandled exception anywhere in the packet pipeline (STUN, RTP, RTCP, DTLS demux, SRTP, TURN) became a channel teardown.\n\n### Fix\n\n- `UdpReceiver.EndReceiveFrom`: a non-socket exception now logs and drops the single packet and re-arms the receive loop (matching the existing `SIPUDPChannel` behaviour), instead of closing the channel. Genuine socket failures continue to be handled separately.\n- `RTPChannel.OnRTPPacketReceived`: requires a minimum packet length (`RTPHeader.MIN_HEADER_LEN`) before indexing the discriminator bytes.\n- STUN parsing: `ParseMessageAttributes` validates each attribute value length and skips malformed/truncated attributes; the XOR/address attribute constructors validate length defensively; `ParseSTUNMessage` no longer dereferences a null attribute list.\n\nRegression tests were added covering the 1-byte packet (channel stays open and remains usable), short/zero-length XOR address attributes (0–7 bytes), and truncated STUN messages.\n\n### Workarounds\n\nNone within the library short of upgrading. Restricting the RTP/ICE port to known peers at the network layer reduces exposure but does not eliminate it, since a negotiating peer can still trigger the condition.\n\n### Credit\n\nResponsibly reported by Lokhesh Ujhoodha.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "NuGet",
      "name" : "SIPSorcery"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "10.0.9"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 10.0.8"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sipsorcery-org/sipsorcery/security/advisories/GHSA-28gm-jrmw-xx93"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sipsorcery-org/sipsorcery/pull/1677"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sipsorcery-org/sipsorcery/commit/bdb76cbc0c7216e3126f743fb78e8525af56cea2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sipsorcery-org/sipsorcery"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-755" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-28T17:01:19Z",
    "nvd_published_at" : null
  }
}