Service interruption via unbounded token splitting
Published Mar 21, 2025 · Updated Apr 10, 2025
Resource exhaustion in golang-jwt jwt 3.2.0 through 4.5.1 and 5.0.0-rc.1 through 5.2.1 allows remote attackers to interrupt services. Parser.ParseUnverified uses strings.Split on the entire untrusted token, allocating a slice entry for every period before rejecting extra segments. Any unauthenticated endpoint that passes a crafted Bearer token to this function can exhaust application memory and interrupt the hosting service.
Summary
What happened
Resource exhaustion in golang-jwt jwt 3.2.0 through 4.5.1 and 5.0.0-rc.1 through 5.2.1 allows remote attackers to interrupt services. Parser.ParseUnverified uses strings.Split on the entire untrusted token, allocating a slice entry for every period before rejecting extra segments. Any unauthenticated endpoint that passes a crafted Bearer token to this function can exhaust application memory and interrupt the hosting service.
The record
- CVE
- CVE-2025-30204
- Published
- Mar 21, 2025
- Updated
- Apr 10, 2025
- Vendor
- golang-jwt
- Product
- jwt
- Classifications
- CWE-405, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 21, 2025CVE publishedPublication date reported by the CVE source.
- Apr 10, 2025Record 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=>= 3.2.0, < 4.5.2
- Affected versionversion=>= 5.0.0-rc.1, < 5.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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