Signature acceptance via lenient PKCS#1 padding parsing
Published Apr 7, 2021 · Updated Aug 3, 2024
Improper RSA signature verification in jsrsasign for Node.js 10.1.13 and earlier allows attackers to have malformed signatures accepted as valid. RSAKey.prototype.verify strips the decoded message prefix with an incorrect regular expression without enforcing the leading byte, block type, or minimum padding length. Constructing a practical forgery still depends on a hash collision, and no practical attack is known.
Summary
What happened
Improper RSA signature verification in jsrsasign for Node.js 10.1.13 and earlier allows attackers to have malformed signatures accepted as valid. RSAKey.prototype.verify strips the decoded message prefix with an incorrect regular expression without enforcing the leading byte, block type, or minimum padding length. Constructing a practical forgery still depends on a hash collision, and no practical attack is known.
The record
- CVE
- CVE-2021-30246
- Published
- Apr 7, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- PKCS#1 v1.5 malformed-signature test vectorsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo