Memory corruption via wrapped query length calculation
Published May 3, 2024 · Updated Nov 4, 2025
Integer overflow in uriparser 0 through 0.9.7 allows attackers to corrupt memory by composing a query with an overlong key or value. ComposeQueryEngine casts URI_STRLEN results to int before checking them against INT_MAX, so inputs longer than INT_MAX wrap and corrupt the output-size calculation. A consuming application must pass a key or value longer than INT_MAX; the resulting undersized buffer can crash the process or corrupt adjacent memory.
Summary
What happened
Integer overflow in uriparser 0 through 0.9.7 allows attackers to corrupt memory by composing a query with an overlong key or value. ComposeQueryEngine casts URI_STRLEN results to int before checking them against INT_MAX, so inputs longer than INT_MAX wrap and corrupt the output-size calculation. A consuming application must pass a key or value longer than INT_MAX; the resulting undersized buffer can crash the process or corrupt adjacent memory.
The record
- CVE
- CVE-2024-34402
- Published
- May 3, 2024
- Updated
- Nov 4, 2025
- Vendor
- uriparser project
- Product
- uriparser
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=0 <=0.9.7
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