Incorrect RFC 3986 URI serialization for oversized input
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| PHP Group | PHP | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Incorrect RFC 3986 URI serialization for oversized input. The Uri\Rfc3986\Uri class does not correctly handle the output-size limit and errors of the uriparser library when converting a URI back to a string. For a URI whose string representation reaches approximately 2 GiB, toString(), toRawString() and other serializing operations can return a truncated or invalid string instead of an error. An application that accepts attacker-controlled URI data of that size, has enough memory to process it and trusts the result may make incorrect validation or routing decisions, and the large allocations can exhaust memory. parse_url() and Uri\WhatWg\Url are not affected. This issue affects PHP versions 8.5.* before 8.5.13. | |
| Title | Incorrect RFC 3986 URI serialization for oversized input | |
| First Time appeared |
Php
Php php |
|
| Weaknesses | CWE-190 CWE-252 |
|
| CPEs | cpe:2.3:a:php:php:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Php
Php php |
|
| References |
| |
| Metrics |
cvssV4_0
|