Incorrect Default Permissions

Opis

During installation, installed file permissions are set to allow anyone to modify those files.

Skutki

• Confidentiality, Integrity

  Read Application Data; Modify Application Data

Zapobieganie

• Architecture and Design, Operation

  The architecture needs to access and modification attributes for files to only those users who actually require those actions.

• Architecture and Design · Separation of Privilege

  Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

  Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Przykłady podatności

• CVE-2005-1941 Executables installed world-writable.
• CVE-2002-1713 Home directories installed world-readable.
• CVE-2001-1550 World-writable log files allow information loss; world-readable file has cleartext passwords.
• CVE-2002-1711 World-readable directory.
• CVE-2002-1844 Windows product uses insecure permissions when installing on Solaris (genesis: port error).
• CVE-2001-0497 Insecure permissions for a shared secret key file. Overlaps cryptographic problem.
• CVE-1999-0426 Default permissions of a device allow IP spoofing.

Słabość nadrzędna

• CWE-732 Incorrect Permission Assignment for Critical Resource

Kiedy powstaje

• Architecture and Design
• Implementation
• Installation
• Operation

Dotyczy

Not Language-Specific, Not Technology-Specific, ICS/OT

Uwagi

As of CWE 4.19, this entry is being considered for deprecation or significant revision. Its name and description are inconsistent. The name is more general, and the description is more specific. The description emphasizes the installation phase only; mentions only files; and emphasizes modification of those files. The name applies to any type of resource, does not mention the specific permissions, and could be relevant to any SDLC phase.

Źródła

1. The Art of Software Security Assessment — Mark Dowd, John McDonald, Justin Schuh, Chapter 3, "Insecure Defaults", Page 69, Addison Wesley, 2006
2. State-of-the-Art Resources (SOAR) for Software Vulnerability Detection, Test, and Evaluation — Gregory Larsen, E. Kenneth Hong Fong, David A. Wheeler, Rama S. Moorthy, 2014
3. State-of-the-Art Resources (SOAR) for Software Vulnerability Detection, Test, and Evaluation — Gregory Larsen, E. Kenneth Hong Fong, David A. Wheeler, Rama S. Moorthy, 2014