CWE-1327: Binding to an Unrestricted IP Address

Extended 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.

Code Examples & CVEs

Demonstrative Examples

The following code snippet uses 0.0.0.0 in a Puppet script.

The Puppet code snippet is used to provision a signing server that will use 0.0.0.0 to accept traffic. However, as 0.0.0.0 is unrestricted, malicious users may use this IP address to launch frequent requests and cause denial of service attacks.

BadOther

signingserver::instance { 					 					  "nightly-key-signing-server": 					   					  listenaddr     => "0.0.0.0", 					  port           => "9100", 					  code_tag       => "SIGNING_SERVER", 					   					  }

The following code snippet uses 0.0.0.0 in a Puppet script.

GoodOther

signingserver::instance { 					 					  "nightly-key-signing-server": 					   					  listenaddr     => "127.0.0.1", 					  port           => "9100", 					  code_tag       => "SIGNING_SERVER", 					   					  }

Observed CVE Examples (2)

CVE-2023-41742

cybersecurity product binds to an unrestricted IP address

View Details

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.

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1327 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1327, Binding to an Unrestricted IP Address, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Apply Firewall controls for Binding to an Unrestricted IP Address

MITRE associates mitigation with System Configuration; the listed strategies include Firewall; recorded impacts include DoS: Amplification. Use these source-defined anchors to turn CWE-1327 into implementation, review, and verification checks for the affected component.

CWE-1327: Binding to an Unrestricted IP Address — MITRE CWE

Triage CWE-1327 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1327, Binding to an Unrestricted IP Address, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1327

Apply MITRE's full root-cause mapping guidance when using CWE-1327, Binding to an Unrestricted IP Address. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-1327 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1327, Binding to an Unrestricted IP Address. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-1327: Binding to an Unrestricted IP Address?+

CWE-1327: Binding to an Unrestricted IP Address is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely. 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.

What are the security consequences of Binding to an Unrestricted IP Address?+

If exploited, CWE-1327 (Binding to an Unrestricted IP Address) it can compromise Availability, leading to outcomes such as DoS: Amplification.

How do you prevent or mitigate Binding to an Unrestricted IP Address?+

Recommended mitigations for CWE-1327 include: Assign IP addresses that are not 0.0.0.0. Unwanted connections to the configured server may be denied through a firewall or other packet filtering measures.

Which programming languages are affected by Binding to an Unrestricted IP Address?+

CWE-1327 commonly affects Other. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Binding to an Unrestricted IP Address?+

MITRE documents real CVEs mapped to CWE-1327, including CVE-2023-41742 and CVE-2022-21947. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1327 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-1327: Binding to an Unrestricted IP Address

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Likelihood

Mitigation Strategies

Phase

Description

Effectiveness