Go JOSE's Parsing Vulnerable to Denial of Service
go-jose
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-jose/go-jose/v4 Go |
|
|
| github.com/go-jose/go-jose/v3 Go |
|
|
| github.com/go-jose/go-jose Go |
go-jose
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-jose/go-jose/v4 Go |
|
|
| github.com/go-jose/go-jose/v3 Go |
|
|
| github.com/go-jose/go-jose Go |
|
|
| github.com/square/go-jose Go |
| No fix yet |
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.
From the CVE record · GitHub_M
Go JOSE can consume excessive memory while parsing compact JWS or JWE tokens containing many `.` characters. An attacker who can submit maliciously crafted tokens could send numerous malformed tokens and cause memory exhaustion and denial of service.
Check applications using github.com/go-jose/go-jose/v4 before 4.0.5, github.com/go-jose/go-jose/v3 before 3.0.4, github.com/go-jose/go-jose before 3.0.4, or any version of github.com/square/go-jose.