Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge did not validate the AES-GCM tagLength option passed to start() during decryption through forge.cipher.createDecipher(). When an application derived tagLength from received data or used an unset or zero-like configuration value, a value that converted to zero together with an empty or missing authentication tag caused the calculated and supplied tags to compare as empty, so decipher.finish() accepted unauthenticated ciphertext. Applications that omit tagLength to use the 128-bit default or pass a fixed valid tag length are unaffected. This issue is fixed in version 1.4.1.
Weakness
The product does not validate or incorrectly validates the integrity check values or “checksums” of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
Potential Mitigations
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/145.html
- https://cwe.mitre.org/data/definitions/463.html
- https://cwe.mitre.org/data/definitions/75.html
References
- https://github.com/digitalbazaar/forge/commit/236845d96c71207259f91638d0138bba8e2fd624
- https://github.com/digitalbazaar/forge/releases/tag/v1.4.1
- https://github.com/digitalbazaar/forge/security/advisories/GHSA-5cwg-6vw7-rj6p
- https://github.com/digitalbazaar/forge/security/advisories/GHSA-5cwg-6vw7-rj6p