CWE-276: Incorrect Default Permissions | Glexia
CWE-276 (Incorrect Default Permissions) weakness overview with consequences, detection methods, mitigations, related CVEs and MITRE ATT&CK context.
Glexia's Take · Automated analysis
CWE-276: Incorrect Default Permissions
Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Confidentiality,Integrity: Read Application Data,Modify Application Data
Developer Pattern
CWE-276 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Automation confidence
high confidence from CWE-276, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-276: Incorrect Default Permissions
During installation, installed file permissions are set to allow anyone to modify those files.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- Missing validation
- Unsafe defaults
- Insufficient authorization or memory-safety invariant
Remediation
- 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:
Detection
- Automated Static Analysis - Binary or Bytecode:
- Manual Static Analysis - Binary or Bytecode:
- Dynamic Analysis with Automated Results Interpretation:
- Dynamic Analysis with Manual Results Interpretation:
- Manual Static Analysis - Source Code:
- Automated Static Analysis - Source Code:
- Automated Static Analysis:
- Architecture or Design Review:
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.