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.
                
            References
                    | Link | Resource | 
|---|---|
| https://github.com/kjur/jsrsasign/releases/tag/8.0.17 | Release Notes Third Party Advisory | 
| https://github.com/kjur/jsrsasign/issues/438 | Exploit Issue Tracking Third Party Advisory | 
| https://github.com/kjur/jsrsasign/releases/tag/8.0.18 | Release Notes Third Party Advisory | 
| https://www.npmjs.com/package/jsrsasign | Product Third Party Advisory | 
| https://kjur.github.io/jsrsasign/ | Release Notes Third Party Advisory | 
| https://security.netapp.com/advisory/ntap-20200724-0001/ | Third Party Advisory | 
Information
                Published : 2020-06-22 05:15
Updated : 2023-01-27 12:52
NVD link : CVE-2020-14968
Mitre link : CVE-2020-14968
JSON object : View
CWE
                
                    
                        
                        CWE-119
                        
            Improper Restriction of Operations within the Bounds of a Memory Buffer
Products Affected
                jsrsasign_project
- jsrsasign
 
netapp
- max_data
 


