SIPGO
SIPGO: DoS via unvalidated WebSocket frame length
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-789
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
emiago sipgo
- < 1.4.3
Fixed in 1.4.3
Mitigation
Upgrade sipgo to 1.4.3 or later.
References
- Vendor advisory github.com/emiago/sipgo/security/advisories/GH…
- Patch github.com/emiago/sipgo/commit/769e4bc958376e2…
- Release notes github.com/emiago/sipgo/releases/tag/v1.4.3
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.