CWE-1327 Detail

CWE-1327

Binding to an Unrestricted IP Address
Incomplete
2020-12-10
00h00 +00:00
2023-10-26
00h00 +00:00
CWE Mitre.org
Notifications for a CWE
Stay informed of any changes for a specific CWE.
Notifications manage

Name: Binding to an Unrestricted IP Address

The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely.

CWE Description

When a server binds to the address 0.0.0.0, it allows connections from every IP address on the local machine, effectively exposing the server to every possible network. This might be much broader access than intended by the developer or administrator, who might only be expecting the server to be reachable from a single interface/network.

General Informations

Modes Of Introduction

System Configuration

Applicable Platforms

Language

Name: Other (Undetermined)

Operating Systems

Class: Not OS-Specific (Undetermined)

Architectures

Class: Not Architecture-Specific (Undetermined)

Technologies

Name: Web Server (Undetermined)
Class: Client Server (Undetermined)
Class: Cloud Computing (Undetermined)

Common Consequences

Scope Impact Likelihood
AvailabilityDoS: AmplificationHigh

Observed Examples

References Description

CVE-2022-21947

Desktop manager for Kubernetes and container management binds a service to 0.0.0.0, allowing users on the network to make requests to a dashboard API.

Potential Mitigations

Phases : System Configuration
Assign IP addresses that are not 0.0.0.0.
Phases : System Configuration
Unwanted connections to the configured server may be denied through a firewall or other packet filtering measures.

Vulnerability Mapping Notes

Justification : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comment : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Related Attack Patterns

CAPEC-ID Attack Pattern Name
CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs
In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.

References

REF-1158

Security Smells in Ansible and Chef Scripts: A Replication Study
Akond Rahman, Md Rayhanur Rahman, Chris Parnin, Laurie Williams.
https://arxiv.org/pdf/1907.07159.pdf

REF-1159

The Seven Sins: Security Smells in Infrastructure as Code Scripts
Akond Rahman, Chris Parnin, Laurie Williams.
https://dl.acm.org/doi/10.1109/ICSE.2019.00033

Submission

Name Organization Date Date release Version
Akond Rahman Tennessee Technological University 2020-09-08 +00:00 2020-12-10 +00:00 4.3

Modifications

Name Organization Date Comment
CWE Content Team MITRE 2021-03-15 +00:00 updated Relationships
CWE Content Team MITRE 2023-04-27 +00:00 updated Relationships
CWE Content Team MITRE 2023-06-29 +00:00 updated Mapping_Notes
CWE Content Team MITRE 2023-10-26 +00:00 updated Observed_Examples