343 matches found
Security Bulletin: IBM Planning Analytics Cartridge for IBM Cloud Pak for Data 4.8.3 has addressed security vulnerabilities
Summary IBM Planning Analytics Cartridge for IBM Cloud Pak for Data is affected, but not classified as vulnerable based on current information, by a vulnerability in go-jose XFID: 273242. This vulnerability has been addressed by upgrading to a non-vulnerable version of go-jose. Additionally, IBM...
Denial Of Service (DoS)
github.com/go-jose/go-jose is vulnerable to Billion Hashes Attack. The vulnerability is due to the decryptKey function in symmetric.go because it only checks if the value of p2c is a positive integer, but lacks a maximum size check. This allow an attacker to provide a PBES2 encrypted JWE blob wit...
Decryption of malicious PBES2 JWE objects can consume unbounded system resources
The go-jose package is subject to a "billion hashes attack" causing denial-of-service when decrypting JWE inputs. This occurs when an attacker can provide a PBES2 encrypted JWE blob with a very large p2c value that, when decrypted, produces a denial-of-service...
GHSA-2C7C-3MJ9-8FQH Decryption of malicious PBES2 JWE objects can consume unbounded system resources
The go-jose package is subject to a "billion hashes attack" causing denial-of-service when decrypting JWE inputs. This occurs when an attacker can provide a PBES2 encrypted JWE blob with a very large p2c value that, when decrypted, produces a denial-of-service...
GO-2023-2334 Denial of service via decryption of malicious PBES2 JWE objects in github.com/go-jose/go-jose/v3
The go-jose package is subject to a "billion hashes attack" causing denial-of-service when decrypting JWE inputs. This occurs when an attacker can provide a PBES2 encrypted JWE blob with a very large p2c value that, when decrypted, produces a denial-of-service...
GO-2022-0945 Signature validation bypass in gopkg.in/square/go-jose.v1
The go-jose library suffers from multiple signatures exploitation. When validating a signed message, the API did not indicate which signature was valid, which creates the potential for confusion...
GHSA-86R9-39J9-99WP Elliptic Curve Key Disclosure in go-jose
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 ...
Elliptic Curve Key Disclosure in go-jose
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 ...
Integer Overflow in go-jose
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...
GHSA-3FX4-7F69-5MMG Integer Overflow in go-jose
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...
Inadequate Encryption Strength
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 ...
Go JOSE Signature Validation Bypass
Go JOSE before 1.1.0 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...
GHSA-77GC-FJ98-665H Go JOSE Signature Validation Bypass
Go JOSE before 1.1.0 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...
Improper Access Control
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...
GO-2020-0009 Integer overflow in github.com/square/go-jose
On 32-bit platforms an attacker can manipulate a ciphertext encrypted with AES-CBC with HMAC such that they can control how large the input buffer is when computing the HMAC authentication tag. This can can allow a manipulated ciphertext to be verified as authentic, opening the door for padding...
Signature Exploitation
github.com/square/go-jose is vulnerable to signature exploitation attacks. During the validation of a signed message, the API does not indicate whether the signature is valid or not. This may lead to confusion if another library assumes the signatures attached are the ones that were originally...
Denial Of Service (DoS) Through An Integer Overflow
github.com/square/go-jose is vulnerable to a CBC-HMAC integer overflow. On an 32-bit architecture, the integer overflow can lead to authentication bypass attacks...
go-jose CBC-HMAC Integer Overflow Vulnerability
go-jose is a standard method for implementing JavaScript object signing and encryption . An integer overflow vulnerability exists in 32-bit architectures in versions of go-jose prior to 1.0.5. An attacker could exploit this vulnerability to bypass authentication...
go-jose encryption issue vulnerability
go-jose is a standard method for implementing JavaScript object signing and encryption . A cryptographic issue vulnerability exists in go-jose that stems from the program failing to validate the cryptographic public key. An attacker can exploit this vulnerability to break the curve encryption...
go-jose signature obfuscation vulnerability
go-jose is a standard method for implementing JavaScript object signing and encryption . A security vulnerability exists in go-jose. As the program fails to verify the validity of the signature. An attacker could exploit the vulnerability to read unauthorized data...