Skip to content
Fencer Intel
medium —

GHSA-2c7c-3mj9-8fqh json

Decryption of malicious PBES2 JWE objects can consume unbounded system resources

published 2y ago modified 2mo ago also GO-2023-2334

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/go-jose/go-jose/v3 3.0.1
  • go github.com/square/go-jose 2.6.2

Is GHSA-2c7c-3mj9-8fqh in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/go-jose/go-jose/v3
<3.0.1
3.0.1
go github.com/square/go-jose
<2.6.2
all versions
2.6.2

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.