Skip to content
Fencer Intel
medium 5.9

GHSA-g753-jx37-7xwh json

ECDSA signature vulnerability of Minerva timing attack in jsrsasign

published 6y ago modified 5y ago

cvss
5.9
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact ECDSA side-channel attack named [Minerava](https://minerva.crocs.fi.muni.cz/) have been found and it was found that it affects to jsrsasign.

Execution time of thousands signature generation have been observed then EC private key which is scalar value may be recovered since point and scalar multiplication time depends on bits of scalar. In jsrsasign 8.0.13 or later, execution time of EC point and scalar multiplication is almost constant and fixed for the issue.

- Minerva is one of timing attack or side channel attack for EC. - If you don't use ECDSA class, you are not affected the vulnerability. - The vulnerability is that attacker may guess private key by checking processing time of EC key generation or ECDSA signing. - The cause issue is that point multiplication processing time in ECDSA signing is depends on private key value. - After 8.0.13, processing time of point multiplication in ECDSA signing have become constant for key value in theory.

### Patches Users using ECDSA signature generation should upgrade to 8.0.13 or later.

### Workarounds There is no workarounds in jsrsasign. Update jsrsasign or use other ECDSA library.

### ACKNOWLEDGEMENT Thanks to Jan Jancar @J08nY, Petr Svenda and Vladimir Sedlacek of Masaryk University in Czech Republic to find and report this vulnerability.

### References https://minerva.crocs.fi.muni.cz/ https://www.npmjs.com/advisories/1505 https://github.com/kjur/jsrsasign/issues/411

Patch / fix

  • npm jsrsasign 8.0.13

Is GHSA-g753-jx37-7xwh 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

CVSS scores

assigned by version score vector
GitHub 3.1 5.9 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm jsrsasign
>=4.0.0, <8.0.13
8.0.13

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

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.

The maintainers of kjur/jsrsasign published their own advisory on GitHub. Reviewed sources take precedence over it.