Files or Directories Accessible to External Parties

Opis

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

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.

Skutki

• Confidentiality, Integrity

  Read Files or Directories; Modify Files or Directories

Zapobieganie

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

Przykłady podatności

• CVE-2005-1835 Data file under web root.

Słabość nadrzędna

• CWE-668 Exposure of Resource to Wrong Sphere
• CWE-285 Improper Authorization

Słabości podrzędne

• CWE-219 Storage of File with Sensitive Data Under Web Root
• CWE-220 Storage of File With Sensitive Data Under FTP Root
• CWE-527 Exposure of Version-Control Repository to an Unauthorized Control Sphere
• CWE-528 Exposure of Core Dump File to an Unauthorized Control Sphere
• CWE-529 Exposure of Access Control List Files to an Unauthorized Control Sphere
• CWE-530 Exposure of Backup File to an Unauthorized Control Sphere
• CWE-539 Use of Persistent Cookies Containing Sensitive Information
• CWE-553 Command Shell in Externally Accessible Directory

Kiedy powstaje

• Architecture and Design
• Implementation — OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.
• Operation — OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.

Dotyczy

Not Language-Specific, Not Technology-Specific, Cloud Computing

Źródła

1. CIS Microsoft Azure Foundations Benchmark version 1.5.0 — Center for Internet Security, Section 3.7, 2022
2. CIS Google Cloud Computing Platform Benchmark version 1.3.0 — Center for Internet Security, Section 5.1, 2022