CWE-412: Unrestricted Externally Accessible Lock | Codefreex Skip to content

Security weakness

CWE-412 Unrestricted Externally Accessible Lock

A base-level weakness that can lead to downtime and lost sales. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is 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.

Business impact

What CWE-412 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • DoS: Resource Consumption (Other)

Free security check

Is CWE-412 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines 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.

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.

Weakness ID
CWE-412
Type
Base
Status
Incomplete
Introduced during
Architecture and Design, Implementation

Prevention

How to fix CWE-412, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • Use any access control that is offered by the functionality that is offering the lock.
    • Use unpredictable names or identifiers for the locks. This might not always be possible or feasible.
    • Consider modifying your code to use non-blocking synchronization methods.

Detection and evidence

How CWE-412 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • White BoxAutomated 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.

Real vulnerabilities it caused

  • CVE-2001-0682Program can not execute when attacker obtains a mutex.
  • CVE-2002-1914Program can not execute when attacker obtains a lock on a critical output file.
  • CVE-2002-1915Program can not execute when attacker obtains a lock on a critical output file.
  • CVE-2002-0051Critical file can be opened with exclusive read access by user, preventing application of security policy. Possibly related to improper permissions, large-window race condition.
  • CVE-2000-0338Chain: predictable file names used for locking, allowing attacker to create the lock beforehand. Resultant from permissions and randomness.
  • CVE-2000-1198Chain: Lock files with predictable names. Resultant from randomness.

How we fix it

From finding to fixed: how Codefreex closes CWE-412

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

Related weaknesses

FAQ

CWE-412: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-412?

CWE-412, “Unrestricted Externally Accessible Lock”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. 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.

How serious is CWE-412?

It can affect availability, with impacts such as dos: resource consumption (other). The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-412?

Use any access control that is offered by the functionality that is offering the lock. Use unpredictable names or identifiers for the locks. This might not always be possible or feasible.

Can Codefreex check my site for CWE-412?

Yes. A senior engineer reviews your site, store or app for CWE-412 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-412 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.