CyberRota Analysis
AI-GeneratedThe vulnerability arises in the fast-uri library, which improperly serializes the port component of a URI, allowing attackers to inject authority delimiters and redirect traffic to a malicious host. This issue primarily impacts applications that construct URIs from untrusted data, particularly those using affected versions of fast-uri prior to the specified fixes. Developers and security teams utilizing fast-uri in their applications should prioritize updating to the patched versions to mitigate the risk of unauthorized access and data manipulation.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
fast-uri serializes the port component of a URI without validating it. When recomposing the authority, the userinfo and host components are escaped but the port is concatenated verbatim, so a port value that is not a sequence of digits can inject authority delimiters, demoting the intended host to userinfo and pointing the authority at an attacker-controlled host. Both fast-uri and Node's URL read the result back as the attacker's host with no error, so re-validating the built URI does not catch it. This affects applications that build URIs from parts and assign untrusted data to the port component through the serialize, normalize, or equal functions in their object forms. The issue affects fast-uri versions before 2.4.6, from 3.0.0 before 3.1.7, and from 4.0.0 before 4.1.4. It is fixed in 2.4.6, 3.1.7, and 4.1.4, where recomposeAuthority rejects any port that is not a digit sequence per RFC 3986.
Related CVEs
Other vulnerabilities affecting the same vendor(s)