CyberRota Analysis
AI-GeneratedThe vulnerability affects the @fastify/forwarded package, specifically in versions prior to 3.0.2, where improper handling of the X-Forwarded-For header allows for the inclusion of horizontal tabs in client IP addresses. This can lead to security evasion in applications that rely on exact string matches for IP-based security measures, such as allowlists or rate limiting. Organizations using affected versions should prioritize upgrading to 3.0.2 or later to mitigate potential security risks.
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
@fastify/forwarded resolves client addresses from the X-Forwarded-For header. In versions before 3.0.2, when the header contains two or more comma separated entries, the parser trims only space characters and does not strip horizontal tabs, even though RFC 7230 defines optional whitespace as both space and tab. As a result, an entry padded with a tab keeps the literal tab in the resolved address string. Applications that make exact string match security decisions on the resolved client IP, such as an allowlist, a blocklist, a per IP rate limit key, or audit log correlation, can be evaded because the tab corrupted string no longer matches the expected value. This does not cross the trust boundary, since a tab corrupted string is not a valid IP and cannot be mistaken for a trusted proxy. The issue is fixed in @fastify/forwarded 3.0.2.
Related CVEs
Other vulnerabilities affecting the same vendor(s)