Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.5

SIPGO 1.4.2 can crash server via WebSocket

published 6 days ago
Summary

The SIPGO library used in older Docker Telegraf images can be tricked into allocating huge amounts of memory when a WebSocket client sends a forged frame size. This can cause the server process to crash or run out of memory. Upgrade to SIPGO version 1.4.3 or later to stop the issue.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.24 docker hardened images telegraf-dev All versions
Docker Hardened Images:Alpine:3.24 docker hardened images telegraf-fips-dev All versions
Docker Hardened Images:Alpine:3.24 docker hardened images telegraf-fips All versions
Docker Hardened Images:Alpine:3.24 docker hardened images telegraf All versions
Original advisory text
SIPGO is a library for writing SIP services in the GO language. Prior to 1.4.3, WSConnection.Read in…
SIPGO is a library for writing SIP services in the GO language. Prior to 1.4.3, WSConnection.Read in sip/transport_ws.go creates a wsutil.Reader without setting MaxFrameSize, allowing NextFrame to accept a client-controlled header.Length before ParseMaxMessageLength is applied. An unauthenticated WS or WSS peer can send a frame header declaring an extremely large payload, causing an oversized allocation or a makeslice length panic before the payload is read and crashing or exhausting memory in the server process. This issue is fixed in version 1.4.3.
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
7.5 High
Timeline
Published12 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta