COMMON WEAKNESS ENUMERATIONIncomplete

CWE-412

Unrestricted Externally Accessible Lock

The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of control.

Soyutlama

Base

Yapı

Simple

Sömürü İhtimali

Medium

Problemi anla

Problem nedir?

The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of control.

Genişletilmiş açıklama

This prevents the product from acting on associated resources or performing other behaviors that are controlled by the presence of the lock. Relevant locks might include an exclusive lock or mutex, or modifying a shared resource that is treated as a lock. If the lock can be held for an indefinite period of time, then the denial of service could be permanent.

Kök neden

Problem nasıl ve ne zaman oluşur?

Yaşam döngüsü evresi

Architecture and Design

Yaşam döngüsü evresi

Implementation

Risk

Başarılı sömürü neye yol açar?

DoS: Resource Consumption (Other)

Etkilenen güvenlik alanları: Availability

When an attacker can control a lock, the program may wait indefinitely until the attacker releases the lock, causing a denial of service to other users of the program. This is especially problematic if there is a blocking operation on the lock.

Savunma

Nasıl önlenir ve çözülür?

Architecture and Design · Implementation

Birden fazla yaşam döngüsü evresinde uygulanacak savunma

Detay
Use any access control that is offered by the functionality that is offering the lock.

Architecture and Design · Implementation

Birden fazla yaşam döngüsü evresinde uygulanacak savunma

Detay
Use unpredictable names or identifiers for the locks. This might not always be possible or feasible.

Architecture and Design

Mimari ve tasarım yaklaşımı

Detay
Consider modifying your code to use non-blocking synchronization methods.

Doğrulama

Nasıl tespit edilir?

White Box

Automated code analysis techniques might not be able to reliably detect this weakness, since the application's behavior and general security model dictate which resource locks are critical. Interpretation of the weakness might require knowledge of the environment, e.g. if the existence of a file is used as a lock, but the file is created in a world-writable directory.