The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a *differen…
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.
https://cwe.mitre.org/data/definitions/177.html →Open in CWE collection →The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component.
https://cwe.mitre.org/data/definitions/838.html →Open in CWE collection →This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
https://capec.mitre.org/data/definitions/64.html →Open in CAPEC collection →This attack targets the encoding of the URL. An adversary can take advantage of the multiple way of encoding an URL and abuse the interpretation of the URL.
https://capec.mitre.org/data/definitions/72.html →Open in CAPEC collection →The adversary utilizes a repeating of the encoding process for a set of characters (that is, character encoding a character encoding of a character) to obfuscate the payload of a particular request. This may allow the adversary to bypass filters that attempt to detect illegal characters or strings, such as those that might be used in traversal or injection attacks. Filters may be able to catch illegal encoded strings, but may not catch doubly encoded strings. For example, a dot (.), often used in path traversal attacks and therefore often blocked by filters, could be URL encoded as %2E. However, many filters recognize this encoding and would still block the request. In a double encoding, the % in the above URL encoding would be encoded again as %25, resulting in %252E which some filters might not catch, but which could still be interpreted as a dot (.) by interpreters on the target.
https://capec.mitre.org/data/definitions/120.html →Open in CAPEC collection →An attacker makes use of Cascading Style Sheets (CSS) injection to steal data cross domain from the victim's browser. The attack works by abusing the standards relating to loading of CSS: 1. Send cookies on any load of CSS (including cross-domain) 2. When parsing returned CSS ignore all data that does not make sense before a valid CSS descriptor is found by the CSS parser.
https://capec.mitre.org/data/definitions/468.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| curl | Tracked | |
| curl | Tracked | |
| curl | Tracked | |
| curl | Tracked | |
| curl | Tracked | |
| curl | Tracked | |
| curl | Tracked | |
| curl | Tracked | |
| clustered_data_ontap | * | Tracked |
| curl | * | Tracked |
| h300s_firmware | * | Tracked |
| h410s_firmware | * | Tracked |
| h500s_firmware | * | Tracked |
| h700s_firmware | * | Tracked |
| hci_bootstrap_os | * | Tracked |
| solidfire,_enterprise_sds_&_hci_storage_node | * | Tracked |
| solidfire_&_hci_management_node | * | Tracked |
| universal_forwarder | * | Tracked |