CVE-2024-34402VulnerabilityPublished 3 May 2024Updated 4 Nov 2025

CVE-2024-34402: uriparser · n/a

Affects uriparserSource CVE Database V5

Not known to be exploited · CVSS 8.6 High : upgrade to 0.9.8 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade uriparser/uriparser to 0.9.8.

Affected software

Product	Affected	Fixed in
GitHuburiparser/uriparser`pkg:github/uriparser/uriparser`Other threats	Affected <0.9.8	Fixed in 0.9.8

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

AI-suggested

European organizations should immediately identify and inventory all software and devices using uriparser, especially versions up to 0.9.7. If you cannot patch yet, implement strict input validation and length checks on URI query parameters at application and network levels to prevent overly long keys or values from being processed. Employ web application firewalls (WAFs) or intrusion prevention systems (IPS) with custom rules to detect and block suspicious URI query patterns indicative of exploitation attempts. Monitor logs for abnormal crashes or memory errors related to URI parsing components. For embedded systems where patching is difficult, consider network segmentation and limiting exposure to untrusted networks. Conduct penetration testing focused on URI parsing to identify potential exploitation paths. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential attacks exploiting this vulnerability.

Description

An issue was discovered in uriparser through 0.9.7. ComposeQueryEngine in UriQuery.c has an integer overflow via long keys or values, with a resultant buffer overflow.

Impact

For European organizations, the impact of CVE-2024-34402 can be significant, especially for those relying on uriparser in network-facing applications, web servers, or embedded devices. Exploitation could lead to denial of service, disrupting critical services and causing operational downtime. More severe exploitation could allow attackers to execute arbitrary code, potentially leading to data breaches, unauthorized access, or lateral movement within networks. Sectors such as finance, telecommunications, healthcare, and critical infrastructure are particularly vulnerable due to their reliance on robust and secure network communications. The vulnerability's remote exploitability without authentication increases the attack surface, making it easier for threat actors to target European organizations. Additionally, the lack of known exploits currently means organizations might be unprepared, increasing risk if exploit code emerges. The potential for widespread impact is heightened by uriparser's integration in various software products, some of which may be embedded in industrial control systems or IoT devices prevalent in Europe.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 17:54 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats