The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a *different* URL usingthe wrong host name when it is later retrieved.For example, a URL like `http://example.com%2F127.0.0.1/`, would be allowed bythe parser and get transposed into `http://example.com/127.0.0.1/`. This flawcan be used to circumvent filters, checks and more.
The product does not properly handle when all or part of an input has been URL encoded.
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
| Link | Tags |
|---|---|
| https://hackerone.com/reports/1553841 | third party advisory exploit |
| https://security.netapp.com/advisory/ntap-20220609-0009/ | third party advisory |
| https://security.gentoo.org/glsa/202212-01 | third party advisory vendor advisory |