Source: golang-github-go-jose-go-jose
Version: 4.0.4-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>

Hi,

The following vulnerability was published for golang-github-go-jose-go-jose.

CVE-2025-27144[0]:
| 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.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2025-27144
    https://www.cve.org/CVERecord?id=CVE-2025-27144
[1] https://github.com/go-jose/go-jose/security/advisories/GHSA-c6gw-w398-hv78
[2] 
https://github.com/go-jose/go-jose/commit/99b346cec4e86d102284642c5dcbe9bb0cacfc22

Regards,
Salvatore

Reply via email to