Description
The product parses numeric input assuming base 10 (decimal) values, but it does not account for inputs that use a different base number (radix).
Frequently, a numeric input that begins with "0" is treated as octal, or "0x" causes it to be treated as hexadecimal, e.g. by the inet_addr() function. For example, "023" (octal) is 35 decimal, or "0x31" is 49 decimal. Other bases may be used as well. If the developer assumes decimal-only inputs, the code could produce incorrect numbers when the inputs are parsed using a different base. This can result in unexpected and/or dangerous behavior. For example, a "0127.0.0.1" IP address is parsed as octal due to the leading "0", whose numeric value would be the same as 87.0.0.1 (decimal), where the developer likely expected to use 127.0.0.1. The consequences vary depending on the surrounding code in which this weakness occurs, but they can include bypassing network-based access control using unexpected IP addresses or netmasks, or causing apparently-symbolic identifiers to be processed as if they are numbers. In web applications, this can enable bypassing of SSRF restrictions.
Potential Impact
Confidentiality
Read Application Data
Integrity
Bypass Protection Mechanism, Alter Execution Logic
Demonstrative Examples
import subprocess
def validate_ip(ip: str):
split_ip = ip.split('.')
if len(split_ip) > 4 or len(split_ip) == 0:
raise ValueError("Invalid IP length")
for octet in split_ip:
try:
int(octet, 10)
except ValueError as e:
raise ValueError(f"Cannot convert IP octet to int - {e}")
# Returns original IP after ensuring no exceptions are raised
return ip
def run_ping(ip: str):
validated = validate_ip(ip)
# The ping command treats zero-prepended IP addresses as octal
result = subprocess.call(["ping", validated])
print(result)import subprocess
import re
def validate_ip_regex(ip: str):
ip_validator = re.compile(r"((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)\.?\b){4}")
if ip_validator.match(ip):
return ip
else:
raise ValueError("IP address does not match valid pattern.")
def run_ping_regex(ip: str):
validated = validate_ip_regex(ip)
# The ping command treats zero-prepended IP addresses as octal
result = subprocess.call(["ping", validated])
print(result)taki.example.com 10.1.0.7
night.example.com 010.1.0.8Mitigations & Prevention
If only decimal-based values are expected in the application, conditional checks should be created in a way that prevent octal or hexadecimal strings from being checked. This can be achieved by converting any numerical string to an explicit base-10 integer prior to the conditional check, to prevent octal or hex values from ever being checked against the condition.
If various numerical bases do need to be supported, check for leading values indicating the non-decimal base you wish to support (such as 0x for hex) and convert the numeric strings to integers of the respective base. Reject any other alternative-base string that is not intentionally supported by the application.
If regular expressions are used to validate IP addresses, ensure that they are bounded using ^ and $ to prevent base-prepended IP addresses from being matched.
Detection Methods
- Automated Static Analysis — Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then sea
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2021-29662 | Chain: Use of zero-prepended IP addresses in Perl-based IP validation module can lead to an access control bypass. |
| CVE-2021-28918 | Chain: Use of zero-prepended IP addresses in a product that manages IP blocks can lead to an SSRF. |
| CVE-2021-29921 | Chain: Use of zero-prepended IP addresses in a Python standard library package can lead to an SSRF. |
| CVE-2021-29923 | Chain: Use of zero-prepended IP addresses in the net Golang library can lead to an access control bypass. |
| CVE-2021-29424 | Chain: Use of zero-prepended IP addresses in Perl netmask module allows bypass of IP-based access control. |
| CVE-2016-4029 | Chain: incorrect validation of intended decimal-based IP address format (CWE-1286) enables parsing of octal or hexadecimal formats (CWE-1389), allowing bypass of an SSRF protection mechanism (CWE-918) |
| CVE-2020-13776 | Mishandling of hex-valued usernames leads to unexpected decimal conversion and privilege escalation in the systemd Linux suite. |
Related Weaknesses
Frequently Asked Questions
What is CWE-1389?
CWE-1389 (Incorrect Parsing of Numbers with Different Radices) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The product parses numeric input assuming base 10 (decimal) values, but it does not account for inputs that use a different base number (radix).
How can CWE-1389 be exploited?
Attackers can exploit CWE-1389 (Incorrect Parsing of Numbers with Different Radices) to read application data. This weakness is typically introduced during the Implementation, Implementation phase of software development.
How do I prevent CWE-1389?
Key mitigations include: If only decimal-based values are expected in the application, conditional checks should be created in a way that prevent octal or hexadecimal strings from being checked. This can be achieved by conver
What is the severity of CWE-1389?
CWE-1389 is classified as a Base-level weakness (Medium abstraction). It has been observed in 7 real-world CVEs.