uriparser: Integer overflow via uriComposeQuery* or uriComposeQueryEx* function
Published Nov 12, 2018
9.8
CRITICALCVSS 3.0
EPSS 2.34%
Description
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.
Affected products
No data.
Configuration 1
- < 0.9.0
Configuration 2
- 8.0
No data.
Red Hat Enterprise Linux 7
uriparser-0:0.7.5-10.el7
Fixed · RHSA-2019:2280
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | uriparser-0:0.7.5-10.el7 | Fixed | RHSA-2019:2280 |
No package ranges for this CVE.
Remediation
Red Hat statement
This issue affects the versions of uriparser as shipped with Red Hat Enterprise Linux 7.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
1 other source (Red Hat) ▾
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
AV:N/AC:L/Au:N/C:P/I:P/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v5
Percentile over time
- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v5
Table of values (19 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 2.34% (0.02338) | 82.98th | v5 (v2026.06.15) |
| Jun 15, 2026 | 2.34% (0.02338) | 81.32th | v5 (v2026.06.15) |
| Jul 20, 2024 | 0.42% (0.00420) | 74.40th | v3 (v2023.03.01) |
| Jul 1, 2024 | 0.42% (0.00420) | 74.31th | v3 (v2023.03.01) |
| Jun 7, 2024 | 0.60% (0.00595) | 78.37th | v3 (v2023.03.01) |
| May 14, 2024 | 0.56% (0.00555) | 77.46th | v3 (v2023.03.01) |
| Apr 4, 2024 | 0.78% (0.00785) | 81.09th | v3 (v2023.03.01) |
| Mar 13, 2024 | 0.98% (0.00979) | 83.05th | v3 (v2023.03.01) |
| Nov 6, 2023 | 0.69% (0.00692) | 78.00th | v3 (v2023.03.01) |
| Jul 8, 2023 | 0.70% (0.00705) | 77.73th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.93% (0.00927) | 80.55th | v3 (v2023.03.01) |
| Mar 6, 2023 | 1.02% (0.01018) | 40.69th | v2 (v2022.01.01) |
| Sep 10, 2022 | 1.02% (0.01018) | 38.88th | v2 (v2022.01.01) |
| Apr 1, 2022 | 1.02% (0.01018) | 36.86th | v2 (v2022.01.01) |
| Feb 4, 2022 | 1.02% (0.01018) | 19.50th | v2 (v2022.01.01) |
| Feb 3, 2022 | 1.04% (0.01040) | 28.32th | v1 |
| Jan 6, 2022 | 1.04% (0.01040) | 27.69th | v1 |
| Sep 1, 2021 | 1.04% (0.01040) | 64.49th | v1 |
| Apr 14, 2021 | 1.04% (0.01040) | 0.00th | v1 |
References (8)
- https://access.redhat.com/errata/RHSA-2019:2280 vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2018-19199 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1651948 Issue Tracking
- https://github.com/uriparser/uriparser/blob/uriparser-0.9.0/ChangeLog x_refsource_MISCPatchThird Party Advisory
- https://github.com/uriparser/uriparser/commit/f76275d4a91b28d687250525d3a0c5509bbd666f x_refsource_MISCPatchThird Party Advisory
- https://lists.debian.org/debian-lts-announce/2018/11/msg00019.html mailing-listx_refsource_MLISTThird Party Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2018-19199
- https://www.cve.org/CVERecord?id=CVE-2018-19199
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/errata/RHSA-2019:2280 | vendor-advisoryx_refsource_REDHAT | |
| https://access.redhat.com/security/cve/CVE-2018-19199 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1651948 | Issue Tracking | |
| https://github.com/uriparser/uriparser/blob/uriparser-0.9.0/ChangeLog | x_refsource_MISCPatchThird Party Advisory | |
| https://github.com/uriparser/uriparser/commit/f76275d4a91b28d687250525d3a0c5509bbd666f | x_refsource_MISCPatchThird Party Advisory | |
| https://lists.debian.org/debian-lts-announce/2018/11/msg00019.html | mailing-listx_refsource_MLISTThird Party Advisory | |
| https://nvd.nist.gov/vuln/detail/CVE-2018-19199 | ||
| https://www.cve.org/CVERecord?id=CVE-2018-19199 |
Change history (0)
No recorded changes yet.