COMMON WEAKNESS ENUMERATIONDraft

CWE-413

Improper Resource Locking

The product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.

Abstraction

Base

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

The product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.

Extended description

When a resource is not properly locked, an attacker could modify the resource while it is being operated on by the product. This might violate the product's assumption that the resource will not change, potentially leading to unexpected behaviors.

Root cause

How and when does the problem arise?

Lifecycle phase

Architecture and Design

Lifecycle phase

Implementation

Risk

What does successful exploitation lead to?

Modify Application DataDoS: InstabilityDoS: Crash, Exit, or Restart

Affected security scopes: Integrity, Availability

Defence

How is it prevented and fixed?

Architecture and Design

Architecture and design approach

Detail
Use a non-conflicting privilege scheme.

Architecture and Design · Implementation

Defence to apply across several lifecycle phases

Detail
Use synchronization when locking a resource.

Verification

How is it detected?

Automated Static Analysis

High
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-413: Common Weakness Enumeration Entry CWE-413 · DayBreach Sözlük · DayBreach