Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)
go-jose
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-jose/go-jose/v4 Go |
|
|
| github.com/go-jose/go-jose/v3 Go |
|
|
| gopkg.in/go-jose/go-jose.v2 Go |
go-jose
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-jose/go-jose/v4 Go |
|
|
| github.com/go-jose/go-jose/v3 Go |
|
|
| gopkg.in/go-jose/go-jose.v2 Go |
|
|
| gopkg.in/square/go-jose.v2 Go |
| No fix yet |
Package jose aims to provide an implementation of the Javascript Object Signing and Encryption set of standards. An attacker could send a JWE containing compressed data that used large amounts of memory and CPU when decompressed by Decrypt or DecryptMulti. Those functions now return an error if the decompressed data would exceed 250kB or 10x the compressed size (whichever is larger). This vulnerability has been patched in versions 4.0.1, 3.0.3 and 2.6.3.
From the CVE record · GitHub_M
go-jose can consume excessive memory and CPU when Decrypt or DecryptMulti decompresses a crafted JWE. An attacker can trigger this by sending such a JWE to an application that decrypts it; the input does not specify whether authentication or user interaction is required.
Check applications using github.com/go-jose/go-jose/v4 before 4.0.1, github.com/go-jose/go-jose/v3 before 3.0.3, gopkg.in/go-jose/go-jose.v2 before 2.6.3, or any version of gopkg.in/square/go-jose.v2.