SIPGO: DoS via unvalidated WebSocket frame length
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| emiago | sipgo | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Emiago | Sipgo |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8h6x-h86x-75wh | SIPGO: DoS via unvalidated WebSocket frame length |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.609% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Emiago
Emiago sipgo |
|
| Vendors & Products |
Emiago
Emiago sipgo |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | SIPGO: DoS via unvalidated WebSocket frame length | |
| Weaknesses | CWE-789 | |
| References |
| |
| Metrics |
cvssV3_1
|