Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CWE-276:Incorrect Default Permissions
Weakness ID:276
Version:v4.17
Weakness Name:Incorrect Default Permissions
Vulnerability Mapping:Allowed
Abstraction:Base
Structure:Simple
Status:Draft
Likelihood of Exploit:Medium
DetailsContent HistoryObserved CVE ExamplesReports
▼Description

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

▼Extended Description

▼Alternate Terms
▼Relationships
Relevant to the view"Research Concepts - (1000)"
NatureMappingTypeIDName
ChildOfAllowed-with-ReviewC732Incorrect Permission Assignment for Critical Resource
Nature: ChildOf
Mapping: Allowed-with-Review
Type: Class
ID: 732
Name: Incorrect Permission Assignment for Critical Resource
▼Memberships
NatureMappingTypeIDName
MemberOfProhibitedC275Permission Issues
MemberOfProhibitedC743CERT C Secure Coding Standard (2008) Chapter 10 - Input Output (FIO)
MemberOfProhibitedC857The CERT Oracle Secure Coding Standard for Java (2011) Chapter 14 - Input Output (FIO)
MemberOfProhibitedC877CERT C++ Secure Coding Section 09 - Input Output (FIO)
MemberOfProhibitedC946SFP Secondary Cluster: Insecure Resource Permissions
MemberOfProhibitedC1011Authorize Actors
MemberOfProhibitedC1147SEI CERT Oracle Secure Coding Standard for Java - Guidelines 13. Input Output (FIO)
MemberOfProhibitedC1198Privilege Separation and Access Control Issues
MemberOfProhibitedV1337Weaknesses in the 2021 CWE Top 25 Most Dangerous Software Weaknesses
MemberOfProhibitedC1345OWASP Top Ten 2021 Category A01:2021 - Broken Access Control
MemberOfProhibitedC1366ICS Communications: Frail Security in Protocols
MemberOfProhibitedC1376ICS Engineering (Construction/Deployment): Security Gaps in Commissioning
MemberOfProhibitedV1387Weaknesses in the 2022 CWE Top 25 Most Dangerous Software Weaknesses
MemberOfProhibitedC1396Comprehensive Categorization: Access Control
MemberOfProhibitedV1425Weaknesses in the 2023 CWE Top 25 Most Dangerous Software Weaknesses
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 275
Name: Permission Issues
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 743
Name: CERT C Secure Coding Standard (2008) Chapter 10 - Input Output (FIO)
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 857
Name: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 14 - Input Output (FIO)
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 877
Name: CERT C++ Secure Coding Section 09 - Input Output (FIO)
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 946
Name: SFP Secondary Cluster: Insecure Resource Permissions
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 1011
Name: Authorize Actors
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 1147
Name: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 13. Input Output (FIO)
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 1198
Name: Privilege Separation and Access Control Issues
Nature: MemberOf
Mapping: Prohibited
Type:View
ID: 1337
Name: Weaknesses in the 2021 CWE Top 25 Most Dangerous Software Weaknesses
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 1345
Name: OWASP Top Ten 2021 Category A01:2021 - Broken Access Control
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 1366
Name: ICS Communications: Frail Security in Protocols
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 1376
Name: ICS Engineering (Construction/Deployment): Security Gaps in Commissioning
Nature: MemberOf
Mapping: Prohibited
Type:View
ID: 1387
Name: Weaknesses in the 2022 CWE Top 25 Most Dangerous Software Weaknesses
Nature: MemberOf
Mapping: Prohibited
Type:Category
ID: 1396
Name: Comprehensive Categorization: Access Control
Nature: MemberOf
Mapping: Prohibited
Type:View
ID: 1425
Name: Weaknesses in the 2023 CWE Top 25 Most Dangerous Software Weaknesses
▼Tags
NatureMappingTypeIDName
MemberOfProhibitedBSBOSS-273Medium likelihood of exploit
MemberOfProhibitedBSBOSS-280Separation of Privilege Strategy
MemberOfProhibitedBSBOSS-294Not Language-Specific Weaknesses
MemberOfProhibitedBSBOSS-305ICS/OT (technology class) Weaknesses
MemberOfProhibitedBSBOSS-307Not Technology-Specific (technology class) Weaknesses
MemberOfProhibitedBSBOSS-318Modify Application Data (impact)
MemberOfProhibitedBSBOSS-328Read Application Data (impact)
Nature: MemberOf
Mapping: Prohibited
Type:BOSSView
ID: BOSS-273
Name: Medium likelihood of exploit
Nature: MemberOf
Mapping: Prohibited
Type:BOSSView
ID: BOSS-280
Name: Separation of Privilege Strategy
Nature: MemberOf
Mapping: Prohibited
Type:BOSSView
ID: BOSS-294
Name: Not Language-Specific Weaknesses
Nature: MemberOf
Mapping: Prohibited
Type:BOSSView
ID: BOSS-305
Name: ICS/OT (technology class) Weaknesses
Nature: MemberOf
Mapping: Prohibited
Type:BOSSView
ID: BOSS-307
Name: Not Technology-Specific (technology class) Weaknesses
Nature: MemberOf
Mapping: Prohibited
Type:BOSSView
ID: BOSS-318
Name: Modify Application Data (impact)
Nature: MemberOf
Mapping: Prohibited
Type:BOSSView
ID: BOSS-328
Name: Read Application Data (impact)
▼Relevant To View
Relevant to the view"Architectural Concepts - (1008)"
NatureMappingTypeIDName
MemberOfProhibitedC1011Authorize Actors
Nature: MemberOf
Mapping: Prohibited
Type: Category
ID: 1011
Name: Authorize Actors
Relevant to the view"Weaknesses Addressed by the SEI CERT Oracle Coding Standard for Java - (1133)"
NatureMappingTypeIDName
MemberOfProhibitedC1147SEI CERT Oracle Secure Coding Standard for Java - Guidelines 13. Input Output (FIO)
Nature: MemberOf
Mapping: Prohibited
Type: Category
ID: 1147
Name: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 13. Input Output (FIO)
Relevant to the view"Hardware Design - (1194)"
NatureMappingTypeIDName
MemberOfProhibitedC1198Privilege Separation and Access Control Issues
Nature: MemberOf
Mapping: Prohibited
Type: Category
ID: 1198
Name: Privilege Separation and Access Control Issues
Relevant to the view"OWASP Top Ten (2021) - (1344)"
NatureMappingTypeIDName
MemberOfProhibitedC1345OWASP Top Ten 2021 Category A01:2021 - Broken Access Control
Nature: MemberOf
Mapping: Prohibited
Type: Category
ID: 1345
Name: OWASP Top Ten 2021 Category A01:2021 - Broken Access Control
Relevant to the view"SEI ETF Categories of Security Vulnerabilities in ICS - (1358)"
NatureMappingTypeIDName
MemberOfProhibitedC1366ICS Communications: Frail Security in Protocols
Nature: MemberOf
Mapping: Prohibited
Type: Category
ID: 1366
Name: ICS Communications: Frail Security in Protocols
Relevant to the view"SEI ETF Categories of Security Vulnerabilities in ICS - (1358)"
NatureMappingTypeIDName
MemberOfProhibitedC1376ICS Engineering (Construction/Deployment): Security Gaps in Commissioning
Nature: MemberOf
Mapping: Prohibited
Type: Category
ID: 1376
Name: ICS Engineering (Construction/Deployment): Security Gaps in Commissioning
Relevant to the view"Software Development - (699)"
NatureMappingTypeIDName
MemberOfProhibitedC275Permission Issues
Nature: MemberOf
Mapping: Prohibited
Type: Category
ID: 275
Name: Permission Issues
Relevant to the view"Software Fault Pattern (SFP) Clusters - (888)"
NatureMappingTypeIDName
MemberOfProhibitedC946SFP Secondary Cluster: Insecure Resource Permissions
Nature: MemberOf
Mapping: Prohibited
Type: Category
ID: 946
Name: SFP Secondary Cluster: Insecure Resource Permissions
▼Background Detail

▼Common Consequences
ScopeLikelihoodImpactNote
ConfidentialityIntegrityN/ARead Application DataModify Application Data
N/A
Scope: Confidentiality, Integrity
Likelihood: N/A
Impact: Read Application Data, Modify Application Data
Note:
N/A
▼Potential Mitigations
Phase:Architecture and Design, Operation
Mitigation ID: MIT-1
Strategy:
Effectiveness:
Description:

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

Note:


Phase:Architecture and Design
Mitigation ID: MIT-46
Strategy: Separation of Privilege
Effectiveness:
Description:

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.

Note:

▼Modes Of Introduction
Phase: Architecture and Design
Note:

N/A

Phase: Implementation
Note:

N/A

Phase: Installation
Note:

N/A

Phase: Operation
Note:

N/A

▼Applicable Platforms
Languages
Class: Not Language-Specific(Undetermined Prevalence)
Technology
Class: Not Technology-Specific(Undetermined Prevalence)
Class: ICS/OT(Undetermined Prevalence)
▼Demonstrative Examples
▼Observed Examples
ReferenceDescription
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.
Reference: CVE-2005-1941
Description:
Executables installed world-writable.
Reference: CVE-2002-1713
Description:
Home directories installed world-readable.
Reference: CVE-2001-1550
Description:
World-writable log files allow information loss; world-readable file has cleartext passwords.
Reference: CVE-2002-1711
Description:
World-readable directory.
Reference: CVE-2002-1844
Description:
Windows product uses insecure permissions when installing on Solaris (genesis: port error).
Reference: CVE-2001-0497
Description:
Insecure permissions for a shared secret key file. Overlaps cryptographic problem.
Reference: CVE-1999-0426
Description:
Default permissions of a device allow IP spoofing.
▼Affected Resources
    ▼Functional Areas
      ▼Weakness Ordinalities
      OrdinalityDescription
      Primary
      N/A
      Ordinality: Primary
      Description:
      N/A
      ▼Detection Methods
      Automated Static Analysis - Binary or Bytecode
      Detection Method ID:
      Description:

      According to SOAR, the following detection techniques may be useful:

      ``` Cost effective for partial coverage: ```

      Inter-application Flow Analysis

      Effectiveness:SOAR Partial
      Note:

      N/A


      Manual Static Analysis - Binary or Bytecode
      Detection Method ID:
      Description:

      According to SOAR, the following detection techniques may be useful:

      ``` Cost effective for partial coverage: ```

      Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies

      Effectiveness:SOAR Partial
      Note:

      N/A


      Dynamic Analysis with Automated Results Interpretation
      Detection Method ID:
      Description:

      According to SOAR, the following detection techniques may be useful:

      ``` Cost effective for partial coverage: ```

      Host-based Vulnerability Scanners - Examine configuration for flaws, verifying that audit mechanisms work, ensure host configuration meets certain predefined criteria Web Application Scanner Web Services Scanner Database Scanners

      Effectiveness:SOAR Partial
      Note:

      N/A


      Dynamic Analysis with Manual Results Interpretation
      Detection Method ID:
      Description:

      According to SOAR, the following detection techniques may be useful:

      ``` Highly cost effective: ```

      Host Application Interface Scanner ``` Cost effective for partial coverage: ```

      Fuzz Tester Framework-based Fuzzer Automated Monitored Execution Forced Path Execution

      Effectiveness:High
      Note:

      N/A


      Manual Static Analysis - Source Code
      Detection Method ID:
      Description:

      According to SOAR, the following detection techniques may be useful:

      ``` Highly cost effective: ```

      Manual Source Code Review (not inspections) ``` Cost effective for partial coverage: ```

      Focused Manual Spotcheck - Focused manual analysis of source

      Effectiveness:High
      Note:

      N/A


      Automated Static Analysis - Source Code
      Detection Method ID:
      Description:

      According to SOAR, the following detection techniques may be useful:

      ``` Cost effective for partial coverage: ```

      Context-configured Source Code Weakness Analyzer

      Effectiveness:SOAR Partial
      Note:

      N/A


      Automated Static Analysis
      Detection Method ID:
      Description:

      According to SOAR, the following detection techniques may be useful:

      ``` Cost effective for partial coverage: ```

      Configuration Checker

      Effectiveness:SOAR Partial
      Note:

      N/A


      Architecture or Design Review
      Detection Method ID:
      Description:

      According to SOAR, the following detection techniques may be useful:

      ``` Highly cost effective: ```

      Formal Methods / Correct-By-Construction ``` Cost effective for partial coverage: ```

      Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)

      Effectiveness:High
      Note:

      N/A

      ▼Vulnerability Mapping Notes
      Usage:Allowed
      Reason:Acceptable-Use
      Rationale:

      This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.

      Comments:

      Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

      Suggestions:
      ▼Notes
      ▼Taxonomy Mappings
      Taxonomy NameEntry IDFitEntry Name
      PLOVERN/AN/AInsecure Default Permissions
      CERT C Secure CodingFIO06-CN/ACreate files with appropriate access permissions
      The CERT Oracle Secure Coding Standard for Java (2011)FIO01-JN/ACreate files with appropriate access permission
      ISA/IEC 62443Part 2-4N/AReq SP.03.08
      ISA/IEC 62443Part 4-2N/AReq CR 2.1
      Taxonomy Name: PLOVER
      Entry ID: N/A
      Fit: N/A
      Entry Name: Insecure Default Permissions
      Taxonomy Name: CERT C Secure Coding
      Entry ID: FIO06-C
      Fit: N/A
      Entry Name: Create files with appropriate access permissions
      Taxonomy Name: The CERT Oracle Secure Coding Standard for Java (2011)
      Entry ID: FIO01-J
      Fit: N/A
      Entry Name: Create files with appropriate access permission
      Taxonomy Name: ISA/IEC 62443
      Entry ID: Part 2-4
      Fit: N/A
      Entry Name: Req SP.03.08
      Taxonomy Name: ISA/IEC 62443
      Entry ID: Part 4-2
      Fit: N/A
      Entry Name: Req CR 2.1
      ▼Related Attack Patterns
      IDName
      CAPEC-1
      Accessing Functionality Not Properly Constrained by ACLs
      CAPEC-127
      Directory Indexing
      CAPEC-81
      Web Server Logs Tampering
      ID: CAPEC-1
      Name: Accessing Functionality Not Properly Constrained by ACLs
      ID: CAPEC-127
      Name: Directory Indexing
      ID: CAPEC-81
      Name: Web Server Logs Tampering
      ▼References
      Reference ID: REF-62
      Title: The Art of Software Security Assessment
      Author: Mark Dowd, John McDonald, Justin Schuh
      Section: Chapter 3, "Insecure Defaults", Page 69
      Publication:
      Publisher:Addison Wesley
      Edition:1st Edition
      URL:
      URL Date:
      Day:N/A
      Month:N/A
      Year:2006
      Details not found