Critical, CVSS 9.1npmAmendedPublished
sha.js is missing type checks leading to hash rewind and passing on crafted data
CVE-2025-9288 · GHSA-95m3-7q98-8xr5
- Affected
- npm sha.js <= 2.4.11
- Fixed in
- 2.4.12· Vendor fix available
- Issue
- This is the same as GHSA-cpq7-6gpm-g9rc but just for sha.js, as it has its own implementation. Missing input type checks can allow types other than a well-formed Buffer or string, resulting in invalid values, hanging and rewinding the hash state (including turning a tagged hash into an untagged hash), or other generally undefined behaviour. Details See PoC PoC Output: Or just: Impact 1. Hash state rewind on {length: -x}. This is behind the PoC above, also this way an attacker can turn a tagged hash in cryptographic libraries into an untagged hash. 2. Value miscalculation, e.g. a collision is generated by { length: buf.length, ...buf, 0: buf[0] + 256 } This will result in the same hash as of buf, but can be treated by other code differently (e.g. bn.js) 4. DoS on {length:'1e99'} 5. On a subsequent system, (2) can turn into matching hashes but different numeric representations, leading to issues up to private key extraction from cryptography libraries (as nonce is often…
Recommended action: Upgrade to 2.4.12 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.