Skip to main content
VulnerabilityPublished

CVE-2024-34403: uriparser

Affects uriparserSource GCVE Database

0
Compare
Authoritative record:CVE-2024-34403· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium : upgrade to 0.9.8-r0 when convenient.

Data as of 7 Nov 2026, 17:17 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.9.8-r0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 May 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 7 Nov 2026.

What to do

Upgrade uriparser to 0.9.8-r0.

Affected software

ProductAffectedFixed in
CleanStarturiparserpkg:apk/cleanstart/uriparserOther threatsAffected
  • <0.9.8-r0
Fixed in
  • 0.9.8-r0

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

AI-suggested

Users should upgrade to uriparser version 0.9.8-r0 or later to remediate this vulnerability. Since a patch is available, applying the official fix is the recommended mitigation.

Description

A security vulnerability was discovered in the uriparser package affecting versions prior to 0.9.8-r0. The flaw does not impact confidentiality or integrity but causes a denial of service (availability impact). A fix is available in version 0.9.8-r0.

References

Community reviews

Loading reviews…