Technical impact
The flaw lies in the decryption routine of node-forge before 1.4.1, where only the last byte of PKCS#7 padding is validated for CBC and ECB modes, ignoring the correctness of the remaining padding bytes. Consequently, an attacker can supply ciphertext with zero, oversized, or mismatched padding. The library will still finish decryption, silently trimming up to four plaintext blocks. Applications that treat successful decryption as proof of valid data will have their integrity compromised, as the plaintext can be corrupted without detection.
Affected Systems
DigitalBazaar's Forge, also known as node-forge, is the affected product. All releases prior to version 1.4.1 are impacted. Systems that integrate node-forge to perform TLS and other cryptographic operations should determine if they use CBC or ECB decryption with PKCS#7 padding and upgrade accordingly.
Risk and Exploitability
The CVSS base score is 3.7, indicating a low severity, but the impact can be significant if an application accepts tampered data as authentic. The EPSS score is < 1%, indicating a very low probability of exploitation, and the vulnerability is not listed in CISA's KEV catalog. Attackers need only to provide crafted ciphertext to an application where node-forge is used for decryption. Because the defect leaks no sensitive state and does not provide code execution, the primary risk lies in integrity failure rather than confidentiality or availability.
Github GHSA