COMMON WEAKNESS ENUMERATIONDraft

CWE-552

Files or Directories Accessible to External Parties

The product makes files or directories accessible to unauthorized actors, even though they should not be.

Soyutlama

Base

Yapı

Simple

Sömürü İhtimali

Medium

Problemi anla

Problem nedir?

The product makes files or directories accessible to unauthorized actors, even though they should not be.

Genişletilmiş açıklama

Web servers, FTP servers, and similar servers may store a set of files underneath a "root" directory that is accessible to the server's users. Applications may store sensitive files underneath this root without also using access control to limit which users may request those files, if any. Alternately, an application might package multiple files or directories into an archive file (e.g., ZIP or tar), but the application might not exclude sensitive files that are underneath those directories. In cloud technologies and containers, this weakness might present itself in the form of misconfigured storage accounts that can be read or written by a public or anonymous user.

Kök neden

Problem nasıl ve ne zaman oluşur?

Yaşam döngüsü evresi

Architecture and Design

Yaşam döngüsü evresi

Implementation

OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.

Yaşam döngüsü evresi

Operation

OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.

Risk

Başarılı sömürü neye yol açar?

Read Files or DirectoriesModify Files or Directories

Etkilenen güvenlik alanları: Confidentiality, Integrity

Savunma

Nasıl önlenir ve çözülür?

Implementation · System Configuration · Operation

Birden fazla yaşam döngüsü evresinde uygulanacak savunma

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

Doğrulama

Nasıl tespit edilir?

Automated Static Analysis

High
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: Common Weakness Enumeration Entry CWE-552 · DayBreach Sözlük · DayBreach