Signatures are mistakenly recognized to be valid in jsrsasign

published 2022-02-09 4y ago modified 2022-02-15 4y ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

In the jsrsasign package through 10.1.13 for Node.js, some invalid RSA PKCS#1 v1.5 signatures are mistakenly recognized to be valid. NOTE: there is no known practical attack.

Patch / fix

fixed in 1 links 2

npm jsrsasign 10.2.0

github.com/kjur/jsrsasign/releases/tag/10.1.13 release
github.com/kjur/jsrsasign/releases/tag/10.2.0 release

Is GHSA-h87q-g2wp-47pj in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	jsrsasign	<10.2.0	10.2.0

Classification

Weakness

CWE-347 Improper Verification of Cryptographic Signature

References

Sources

GitHub Advisory GHSA-h87q-g2wp-47pj

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.