Quick answers
- Is CVE-2024-21484 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-21484 being exploited in the wild.
- How severe is CVE-2024-21484?
- Low severity, with a CVSS score of 3.1, published 19 January 2024.
- Which products and versions are affected?
- jsrsasign (npm) SEMVER:introduced=0,fixed=11.0.0.
- Is there a fix for CVE-2024-21484?
- Yes. jsrsasign (npm): upgrade to 11.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-21484 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2024-21484?
- Check whether you run jsrsasign (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- jsrsasign (npm): upgrade to 11.0.0 or later
npm install jsrsasign@11.0.0
Technical details
The vulnerability is a Marvin attack (CWE-203: Observable Discrepancy) affecting RSA PKCS#1.5 and RSAOAEP decryption implementations in jsrsasign versions prior to 11.0.0. The attack exploits timing differences in the decryption process that leak information about whether padding is valid, allowing an attacker to gradually decrypt ciphertexts through repeated queries over a network. No authentication or user interaction is required; an attacker only needs network access to the decryption endpoint. The vulnerability impacts confidentiality (high) and availability (low), with a CVSS score of 7.5. The fix is available in version 11.0.0.
Affected products
- jsrsasign jsrsasign before 11.0.0
Identifiers
- CVE-2024-21484
- GHSA-rh63-9qcf-83gf
Timeline
- 2024-01-19: disclosed: Advisory published
- 2024-01-17: patched: Fix released in version 11.0.0