What is CWE-560: Use of umask() with chmod-style Argument?

CWE-560: Use of umask() with chmod-style Argument is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product calls umask() with an incorrect argument that is specified as if it is an argument to chmod().

What are the security consequences of Use of umask() with chmod-style Argument?

If exploited, CWE-560 (Use of umask() with chmod-style Argument) it can compromise Confidentiality, Integrity and Access Control, leading to outcomes such as Read Files or Directories, Modify Files or Directories and Bypass Protection Mechanism.

How do you prevent or mitigate Use of umask() with chmod-style Argument?

Recommended mitigations for CWE-560 include: Use umask() with the correct argument.

How is Use of umask() with chmod-style Argument detected?

CWE-560 can be detected using Automated Static Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Use of umask() with chmod-style Argument?

CWE-560 commonly affects C. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?

A CWE (Common Weakness Enumeration) like CWE-560 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-560: Use of umask() with chmod-style Argument

Verify controls for CWE-560 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-560, Use of umask() with chmod-style Argument, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Use of umask() with chmod-style Argument during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Static Analysis; recorded impacts include Read Files or Directories, Modify Files or Directories, and Bypass Protection Mechanism. Use these source-defined anchors to turn CWE-560 into implementation, review, and verification checks for the affected component.

CWE-560: Use of umask() with chmod-style Argument — MITRE CWE

Triage CWE-560 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-560, Use of umask() with chmod-style Argument, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-560

Apply MITRE's full root-cause mapping guidance when using CWE-560, Use of umask() with chmod-style Argument. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-560 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-560, Use of umask() with chmod-style Argument. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

CWE-560: Use of umask() with chmod-style Argument

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Method

Description

Code Examples & CVEs

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-560 with SSDF evidence

Address Use of umask() with chmod-style Argument during Implementation

Triage CWE-560 against known exploitation evidence

Apply precise root-cause mapping to CWE-560

Validate CWE-560 with root-cause mapping checks

Frequently Asked Questions

Learn More