Authentication bypass via non-constant-time signature comparison
Published Feb 8, 2024 · Updated Aug 19, 2024
Timing side channel in Glitched Polygons l8w8jwt 2.2.1 allows remote attackers to bypass JWT authentication via crafted tokens. The signature-verification path compares computed and supplied signatures with memcmp, whose early-exit behavior exposes timing differences. Exploitation requires repeated network access to a consuming application's token-verification interface and permits acceptance of a forged token.
Summary
What happened
Timing side channel in Glitched Polygons l8w8jwt 2.2.1 allows remote attackers to bypass JWT authentication via crafted tokens. The signature-verification path compares computed and supplied signatures with memcmp, whose early-exit behavior exposes timing differences. Exploitation requires repeated network access to a consuming application's token-verification interface and permits acceptance of a forged token.
The record
- CVE
- CVE-2024-25190
- Published
- Feb 8, 2024
- Updated
- Aug 19, 2024
- Vendor
- Glitched Polygons GmbH
- Product
- l8w8jwt
- Classifications
- CWE-203, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.2.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- CVE request timing-attack reportproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo