Skip to main content
VulnerabilityPublished Updated

CVE-2024-25190: l8w8jwt · Observable Discrepancy

Affects l8w8jwtSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npml8w8jwtpkg:npm/l8w8jwtOther threatsAffected
  • =2.2.1
Fixed in–

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

AI-suggested

1. Immediate mitigation involves replacing the non-constant-time memcmp function with a constant-time comparison function specifically designed to prevent timing side channels. Developers should use established cryptographic libraries that provide constant-time comparison utilities. 2. If upgrading or patching the library is not immediately possible, implement additional layers of authentication or rate limiting to reduce the feasibility of timing attacks. 3. Monitor authentication endpoints for abnormal timing patterns or repeated failed attempts that could indicate exploitation attempts. 4. Conduct code reviews and security testing focusing on timing side channels in authentication logic. 5. Engage with the l8w8jwt maintainers or community to track patch releases and apply updates promptly once available. 6. Consider employing Web Application Firewalls (WAFs) with custom rules to detect and block suspicious timing attack patterns. 7. Educate development teams on secure coding practices related to cryptographic comparisons and side channel mitigations to prevent similar vulnerabilities in the future.

Description

l8w8jwt 2.2.1 uses memcmp (which is not constant time) to verify authentication, which makes it easier to bypass authentication via a timing side channel.

References

Community reviews

Loading reviews…