Skip to content

RSA-PSS signature validation vulnerability by prepending zeros in jsrsasign

Critical severity GitHub Reviewed Published Jun 23, 2020 in kjur/jsrsasign • Updated Jan 27, 2023

Package

npm jsrsasign (npm)

Affected versions

>= 3.0.0, < 8.0.16

Patched versions

8.0.17

Description

Impact

Jsrsasign can verify RSA-PSS signature which value can expressed as BigInteger. When there is a valid RSA-PSS signature value, this vulnerability is also accept value with prepending zeros as a valid signature.

  • If you are not use RSA-PSS signature validation, this vulnerability is not affected.
  • Risk to accept a forged or crafted message to be signed is low.
  • Risk to raise memory corruption is low since jsrsasign uses BigInteger class.

Patches

Users using RSA-PSS signature validation should upgrade to 8.0.17.

Workarounds

Reject RSA-PSS signatures with unnecessary prepending zeros.

References

GHSA-q3gh-5r98-j4h3
kjur/jsrsasign#438
https://nvd.nist.gov/vuln/detail/CVE-2020-14968
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14968
https://vuldb.com/?id.157125
https://kjur.github.io/jsrsasign/api/symbols/RSAKey.html#.verifyWithMessageHashPSS

References

Published by the National Vulnerability Database Jun 22, 2020
@kjur kjur published to kjur/jsrsasign Jun 23, 2020
Reviewed Jun 26, 2020
Published to the GitHub Advisory Database Jun 26, 2020
Last updated Jan 27, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

1.656%
(88th percentile)

Weaknesses

CVE ID

CVE-2020-14968

GHSA ID

GHSA-q3gh-5r98-j4h3

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.