LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19199: An issue was discovered in uriparser before 0.9.0.

An issue was discovered in uriparser before 0.9.0. UriQuery.c allows an integer overflow via a uriComposeQuery* or uriComposeQueryEx* function because of an unchecked multiplication.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

uriparser before 0.9.0 has an integer overflow bug in query string composition. An application using this library could mishandle very large query data in affected functions. The provided sources do not assign CVSS, describe business impact, or report active exploitation.

Executive priority

Treat as a dependency hygiene issue with unclear severity. Patch during the normal vulnerability management cycle, escalating only for internet-facing systems or products that process untrusted URI/query data through uriparser.

Technical view

CVE-2018-19199 is in UriQuery.c. The vulnerable uriComposeQuery* and uriComposeQueryEx* functions perform an unchecked multiplication, causing integer overflow in uriparser versions before 0.9.0. The source bundle provides no CWE, CVSS vector, or confirmed exploit details.

Likely exposure

Exposure is most likely indirect: software, appliances, or OS packages that include uriparser before 0.9.0. Systems are most relevant when they compose URI query strings from attacker-controlled or unusually large input.

Exploitation context

The provided sources do not claim active exploitation, and KEV is false. The issue is a library-level memory-safety condition; practical risk depends on whether an application reaches the affected composition functions with untrusted input.

Researcher notes

Key missing evidence: CVSS, CWE, detailed impact, and exploitability analysis. The strongest source-grounded statement is that versions before 0.9.0 contain unchecked multiplication in query composition code, with vendor updates available through Debian and Red Hat.

Mitigation direction

  • Upgrade uriparser to 0.9.0 or later where directly bundled.
  • Apply vendor package updates from Debian, Red Hat, or your operating system vendor.
  • Check vendor advisories for products that embed uriparser.
  • Reduce exposure of inputs reaching URI query composition paths until patched.

Validation and detection

  • Inventory direct and transitive uriparser versions across applications and images.
  • Confirm packaged systems include the Debian or Red Hat security update where applicable.
  • Review application code for uriComposeQuery* and uriComposeQueryEx* usage.
  • Prioritize validation where query composition handles untrusted or large inputs.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-19199 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.