Go-Jose Project Go-Jose vulnerabilities

CVE-2024-28180 [MEDIUM] CWE-409 CVE-2024-28180: Package jose aims to provide an implementation of the Javascript Object Signing and Encryption set o 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 com

CVE-2016-9121 [CRITICAL] CWE-326 CVE-2016-9121: go-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a go-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack.

CVE-2016-9123 [HIGH] CWE-190 CVE-2016-9123: go-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures. An integer ov go-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures. An integer overflow could lead to authentication bypass for CBC-HMAC encrypted ciphertexts on 32-bit architectures.

CVE-2016-9122 [HIGH] CWE-284 CVE-2016-9122: go-jose before 1.0.4 suffers from multiple signatures exploitation. The go-jose library supports mes go-jose before 1.0.4 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from a