Skip to main content
VulnerabilityPublished Updated

CVE-2024-42461: Elliptic allows BER-encoded signatures

Affects ellipticSource GCVE Database

0
Compare
Authoritative record:CVE-2024-42461· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 6.5.7 when convenient.

Data as of 31 Oct 2026, 01:25 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.15.3
Patch
Available – fixed in 6.5.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade elliptic to 6.5.7.

Affected software

ProductAffectedFixed in
npmellipticAffected
  • >=5.2.1 <6.5.7
Fixed in
  • 6.5.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and the issue is fixed in Elliptic version 6.5.7. Users should upgrade to version 6.5.7 or later to remediate this vulnerability. No additional mitigation steps are indicated.

Description

CVE-2024-42461 is a medium severity vulnerability in the Elliptic package for Node.js versions 5.2.1 up to but not including 6.5.7. It involves ECDSA signature malleability due to acceptance of BER-encoded signatures. This flaw allows signatures to be malleable, which can undermine signature uniqueness and potentially affect cryptographic verification processes. The issue is fixed in version 6.5.7.

References

Community reviews

Loading reviews…