| Name |
Using Alternative IP Address Encodings |
|
| Likelyhood of attack |
Typical severity |
| Medium |
High |
|
| Summary |
This attack relies on the adversary using unexpected formats for representing IP addresses. Networked applications may expect network location information in a specific format, such as fully qualified domains names (FQDNs), URL, IP address, or IP Address ranges. If the location information is not validated against a variety of different possible encodings and formats, the adversary can use an alternate format to bypass application access control. |
| Prerequisites |
The target software must fail to anticipate all of the possible valid encodings of an IP/web address. The adversary must have the ability to communicate with the server. |
| Execution Flow |
| Step |
Phase |
Description |
Techniques |
| 1 |
Explore |
[Survey the application for IP addresses as user input] Using a browser, an automated tool or by inspecting the application, an adversary records all entry points to the application where IP addresses are used. |
- Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
- Use a proxy tool to record all user input entry points visited during a manual traversal of the web application.
- Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.
- Manually inspect the application to find entry points.
|
| 2 |
Experiment |
[Probe entry points to locate vulnerabilities] The adversary uses the entry points gathered in the "Explore" phase as a target list and attempts alternate IP address encodings, observing application behavior. The adversary will also attempt to access the application through an alternate IP address encoding to see if access control changes |
- Instead of using a URL, use the IP address that the URL resolves to
- Specify a port directly to a URL input
- Omit or add "http://" or "https://" to a URL to see if the application behaves differently
|
| 3 |
Exploit |
[Bypass access control] Using an alternate IP address encoding, the adversary will either access the application or give the alternate encoding as input, bypassing access control restrictions. |
|
|
| Solutions | Design: Default deny access control policies Design: Input validation routines should check and enforce both input data types and content against a positive specification. In regards to IP addresses, this should include the authorized manner for the application to represent IP addresses and not accept user specified IP addresses and IP address formats (such as ranges) Implementation: Perform input validation for all remote content. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-173 |
Improper Handling of Alternate Encoding |
| CWE-291 |
Reliance on IP Address for Authentication |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-267 |
An adversary leverages the possibility to encode potentially harmful input or content used by applications such that the applications are ineffective at validating this encoding standard. |
|