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 searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-552 Base Borrador
Files or Directories Accessible to External Parties
This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.
Definición
What is CWE-552?
This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.
This commonly happens in web servers, FTP servers, or similar systems where files are stored under a publicly accessible root directory. If the application doesn't implement proper access controls, sensitive files placed in or under this directory can be requested and retrieved by unauthorized users. The same risk applies when applications package files into archives (like ZIP or tar files) without first filtering out confidential documents from the included directories.
In modern cloud and container environments, this flaw often appears as misconfigured storage buckets or file shares that are open to public or anonymous access. Managing this at scale is difficult; an ASPM like Plexicus can help you track and remediate these configuration flaws across your entire stack, from code to cloud.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
The following Azure command updates the settings for a storage account:
- 2
However, "Allow Blob Public Access" is set to true, meaning that anonymous/public users can access blobs.
- 3
The command could be modified to disable "Allow Blob Public Access" by setting it to false.
- 4
The following Google Cloud Storage command gets the settings for a storage account named 'BUCKET_NAME':
- 5
Suppose the command returns the following result:
Ejemplo de código vulnerable
Vulnerable Shell
The following Azure command updates the settings for a storage account:
az storage account update --name <storage-account> --resource-group <resource-group> --allow-blob-public-access true Ejemplo de código seguro
Secure Shell
The command could be modified to disable "Allow Blob Public Access" by setting it to false.
az storage account update --name <storage-account> --resource-group <resource-group> --allow-blob-public-access false What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención
How to prevent CWE-552
- Implementation / System Configuration / Operation When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
Señales de detección
How to detect CWE-552
CWE-552
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Preguntas frecuentes ¿Qué es CWE-552?
¿Qué gravedad tiene CWE-552?
¿Qué lenguajes o plataformas se ven afectados por CWE-552?
¿Cómo puedo prevenir CWE-552?
¿Cómo detecta y corrige Plexicus CWE-552?
¿Dónde puedo aprender más sobre CWE-552?
Frequently asked questions
¿Qué es CWE-552?
This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.
¿Qué gravedad tiene CWE-552?
MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.
¿Qué lenguajes o plataformas se ven afectados por CWE-552?
MITRE lists the following affected platforms: Not Technology-Specific, Cloud Computing.
¿Cómo puedo prevenir CWE-552?
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
¿Cómo detecta y corrige Plexicus CWE-552?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-552 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-552?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/552.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-552
CWE-668 Padre
Exposure of Resource to Wrong Sphere
This vulnerability occurs when an application unintentionally makes a resource accessible to users or systems that should not have…
CWE-1189 Hermano
Improper Isolation of Shared Resources on System-on-a-Chip (SoC)
This vulnerability occurs when a System-on-a-Chip (SoC) fails to properly separate shared hardware resources between secure (trusted) and…
CWE-1282 Hermano
Assumed-Immutable Data is Stored in Writable Memory
This vulnerability occurs when data that should be permanent and unchangeable—like a bootloader, device IDs, or one-time configuration…
CWE-1327 Hermano
Binding to an Unrestricted IP Address
This vulnerability occurs when software or a service is configured to bind to the IP address 0.0.0.0 (or :: in IPv6), which acts as a…
CWE-1331 Hermano
Improper Isolation of Shared Resources in Network On Chip (NoC)
This vulnerability occurs when a Network on Chip (NoC) fails to properly separate its internal, shared resources—like buffers, switches,…
CWE-134 Hermano
Use of Externally-Controlled Format String
This vulnerability occurs when a program uses a format string from an untrusted, external source (like user input, a network packet, or a…
CWE-200 Hermano
Exposure of Sensitive Information to an Unauthorized Actor
This weakness occurs when an application unintentionally reveals sensitive data to someone who shouldn't have access to it.
CWE-374 Hermano
Passing Mutable Objects to an Untrusted Method
This vulnerability occurs when a function receives a direct reference to mutable data, such as an object or array, instead of a safe copy…
CWE-375 Hermano
Returning a Mutable Object to an Untrusted Caller
This vulnerability occurs when a method directly returns a reference to its internal mutable data, allowing untrusted calling code to…
Recursos
Further reading
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.