CWE-1327
Binding to an Unrestricted IP Address
Incomplete
2020-12-10
00h00 +00:00
00h00 +00:00
2023-10-26
00h00 +00:00
00h00 +00:00
Notifications pour un CWE
Restez informé de toutes modifications pour un CWE spécifique.
Nom: 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.
Description du CWE
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.
Informations générales
Modes d'introduction
System ConfigurationPlateformes applicables
Langue
Name: Other (Undetermined)Systèmes d’exploitation
Class: Not OS-Specific (Undetermined)Architectures
Class: Not Architecture-Specific (Undetermined)Technologies
Name: Web Server (Undetermined)Class: Client Server (Undetermined)
Class: Cloud Computing (Undetermined)
Conséquences courantes
| Portée | Impact | Probabilité |
|---|---|---|
| Availability | DoS: Amplification | High |
Exemples observés
| Références | 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. |
Mesures d’atténuation potentielles
Phases : System ConfigurationAssign 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.
Notes de cartographie des vulnérabilités
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.Commentaire : 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.
Modèles d'attaque associés
| CAPEC-ID | Nom du modèle d'attaque |
|---|---|
| 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. |
Références
REF-1158
Security Smells in Ansible and Chef Scripts: A Replication StudyAkond 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 ScriptsAkond Rahman, Chris Parnin, Laurie Williams.
https://dl.acm.org/doi/10.1109/ICSE.2019.00033
Soumission
| Nom | Organisation | Date | Date de publication | Version |
|---|---|---|---|---|
| Akond Rahman | Tennessee Technological University | 4.3 |
Modifications
| Nom | Organisation | Date | Commentaire |
|---|---|---|---|
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Observed_Examples |
