Skip to content
OpenAdvisories

Weakness (CWE)

CWE-413: Improper Resource Locking

Base Draft

The product must have exclusive access to a resource, but it does not lock or does not correctly lock that resource.

How to prevent it (2 mitigations)
  1. Architecture and Design

    Use a non-conflicting privilege scheme.

  2. Architecture and Design, Implementation

    Use synchronization when locking a resource.

Source: MITRE CWE-413

9 results · Clear filters · Feed

  • High 8.8

    Out of bound access in PPC due to race condition in global variable access

  • High 8.7

    Squid has Denial of Service in ICP Response handling

    Squid is a caching proxy for the Web. Prior to version 7.5, due to premature release of resource during expected lifetime and heap Use-After-Free bugs, Squid is vulnerable to Denial of Service when handling ICP traffic. This problem allows a remote attacker t…

  • High 7.3

    Inadequate lock protection within Xilinx Run time may allow a local attacker to trigger a Use-After-Free condition pote…

  • High 7.7

    In X.Org X server 20.11 through 21.1.16, when a client application uses easystroke for mouse gestures, the main thread …

  • High 8.6

    The Hub in the Snap One OvrC cloud platform is a device used to centralize and manage nested devices connected to it. A…

  • High 7.5

    Improper Resource Locking vulnerability in Mitsubishi Electric MELSEC iQ-R Series R12CCPU-V firmware versions "16" and …

  • High 8.6

    Cisco IOS XE Software AppNav-XE Denial of Service Vulnerability

    A vulnerability in the AppNav-XE feature of Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause an affected device to reload, resulting in a denial of service (DoS) condition. This vulnerability is due to the incorrect handling of c…

  • High 8.3

    Bitdefender BOX v2 bootstrap update_setup command execution vulnerability (VA-2226)

    An exploitable command execution vulnerability exists in the recovery partition of Bitdefender BOX 2, version 2.0.1.91. The API method `/api/update_setup` does not perform firmware signature checks atomically, leading to an exploitable race condition (TOCTTOU…

  • High 7.8

    An information disclosure vulnerability leading to a potential local escalation of privilege in the procfs service (the…