CWE-732Incorrect Permission Assignment for Critical Resource

Description

Common consequences· 3

• Confidentiality — Read Application Data, Read Files or Directories
  An attacker may be able to read sensitive information from the associated resource, such as credentials or configuration information stored in a file.
• Access Control — Gain Privileges or Assume Identity
  An attacker may be able to modify critical properties of the associated resource to gain privileges, such as replacing a world-writable executable with a Trojan horse.
• Integrity / Other — Modify Application Data, Other
  An attacker may be able to destroy or corrupt critical data in the associated resource, such as deletion of records from a database.

Potential mitigations· 5

• [Implementation]When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user) [REF-62], and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
• [Architecture and Design]Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources. [REF-207]
• [Architecture and Design, Operation]
• [Implementation, Installation]During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
• [System Configuration]For all configuration files, executables, and libraries, make sure that they are only readable and writable by the software's administrator.

Related CAPEC attack patterns· 11

Exploits (incoming)11

Compliance frameworks addressing this (incoming)39

Showing top 30 of 39 by confidence. Click any target to see the full neighbourhood.

(incoming)43

Showing top 30 of 43 by confidence. Click any target to see the full neighbourhood.

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.