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 Rascunho
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.
Definição
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.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 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:
Exemplo de código vulnerável
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 Exemplo 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 verificação de prevenção
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.
Sinais de deteção
How to detect CWE-552
O Plexicus deteta automaticamente o CWE-552 e abre um PR de correção em menos de 60 segundos.
O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.
Perguntas frequentes O que é o CWE-552?
Qual a gravidade do CWE-552?
Que linguagens ou plataformas são afetadas pelo CWE-552?
Como posso prevenir o CWE-552?
Como é que o Plexicus deteta e corrige o CWE-552?
Onde posso saber mais sobre o CWE-552?
Frequently asked questions
O que é o CWE-552?
This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.
Qual a gravidade do CWE-552?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-552?
MITRE lists the following affected platforms: Not Technology-Specific, Cloud Computing.
Como posso prevenir o 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.
Como é que o Plexicus deteta e corrige o CWE-552?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-552 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-552?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/552.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-552
CWE-668 Pai
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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
Pronto quando você estiver
Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.
O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.