An issue was discovered in the jsrsasign package before 8.0.17 for Node.js. Its RSASSA-PSS (RSA-PSS) implementation does not detect signature manipulation/modification by prepending '\0' bytes to a signature (it accepts these modified signatures as valid). An attacker can abuse this behavior in an application by creating multiple valid signatures where only one signature should exist. Also, an attacker might prepend these bytes with the goal of triggering memory corruption issues.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
| Link | Tags |
|---|---|
| https://kjur.github.io/jsrsasign/ | third party advisory release notes |
| https://www.npmjs.com/package/jsrsasign | third party advisory product |
| https://github.com/kjur/jsrsasign/releases/tag/8.0.18 | third party advisory release notes |
| https://github.com/kjur/jsrsasign/releases/tag/8.0.17 | third party advisory release notes |
| https://github.com/kjur/jsrsasign/issues/438 | issue tracking exploit third party advisory |
| https://security.netapp.com/advisory/ntap-20200724-0001/ | third party advisory |