Skip to content
OpenAdvisories

Weakness (CWE)

CWE-250: Execution with Unnecessary Privileges

Base Draft

The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.

How to prevent it (7 mitigations)
  1. Architecture and Design, Operation

    Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.

  2. Architecture and Design

    Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code [REF-76]. Raise privileges as late as possible, and drop them as soon as possible to avoid CWE-271. Avoid weaknesses such as CWE-288 and CWE-420 by protecting all possible communication channels that could interact with the privileged code, such as a secondary socket that is only intended to be accessed by administrators.

  3. Architecture and Design

    Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code [REF-76]. Raise privileges as late as possible, and drop them as soon as possible to avoid CWE-271. Avoid weaknesses such as CWE-288 and CWE-420 by protecting all possible communication channels that could interact with the privileged code, such as a secondary socket that is only intended to be accessed by administrators.

  4. Implementation

    Perform extensive input validation for any privileged code that must be exposed to the user and reject anything that does not fit your strict requirements.

  5. Implementation

    When dropping privileges, ensure that they have been dropped successfully to avoid CWE-273. As protection mechanisms in the environment get stronger, privilege-dropping calls may fail even if it seems like they would always succeed.

  6. Implementation

    If circumstances force you to run with extra privileges, then determine the minimum access level necessary. First identify the different permissions that the software and its users will need to perform their actions, such as file read and write permissions, network socket permissions, and so forth. Then explicitly allow those actions while denying all else [REF-76]. Perform extensive input validation and canonicalization to minimize the chances of introducing a separate vulnerability. This mitigation is much more prone to error than dropping the privileges in the first place.

  7. Operation, System Configuration

    Ensure that the software runs properly under the United States Government Configuration Baseline (USGCB) [REF-199] or an equivalent hardening configuration guide, which many organizations use to limit the attack surface and potential risk of deployed software.

Source: MITRE CWE-250

12 results · Clear filters · Feed

  • High 8.3
    CVE-2026-106378 Public exploit

    Privilege elevation in Sandbox in Google Chrome on on Mac prior to 155.0.8059.39 allowed a remote attacker who had comp…

  • High 7.8
    CVE-2026-8933 Public exploit

    snap-confine Local Privilege Escalation via Capabilities Misconfiguration or Flaw in Execution Environment Setup

    A local privilege escalation vulnerability exists in snap-confine, a set-capabilities core component used internally by Canonical snapd to construct the secure execution environment for snap applications. This vulnerability uniquely affects versions of snap-c…

  • High 8.8
    CVE-2026-41900 Public exploit

    OpenLearnX has Critical Remote Code Execution Through Python Sandbox Escape via Code Execution Environment

    OpenLearnX is an open-source, decentralized learning and assessment platform. Prior to version 2.0.3, a remote code execution (RCE) vulnerability was identified in the OpenLearnX code execution environment, allowing sandbox escape and arbitrary command execut…

  • High 7.3
    CVE-2025-43990 Public exploit

    Dell Command Monitor (DCM), versions prior to 10.12.3.28, contains an Execution with Unnecessary Privileges vulnerabili…

  • High 7.8
    CVE-2025-50505 Public exploit

    Clash Verge Rev thru 2.2.3 (fixed in 2.3.0) forces the installation of system services(clash-verge-service) by default …

  • High 7.8
    CVE-2022-38694 Public exploit

    In BootRom, there is a possible unchecked write address. This could lead to local escalation of privilege with no addit…

  • High 7.8
    CVE-2022-38691 Public exploit

    In BootROM, there is a possible missing validation for Certificate Type 0. This could lead to local escalation of privi…

  • High 7.0
    CVE-2025-6019 Public exploit

    Libblockdev: lpe from allow_active to root in libblockdev via udisks

    A Local Privilege Escalation (LPE) vulnerability was found in libblockdev. Generally, the "allow_active" setting in Polkit permits a physically present user to take certain actions based on the session type. Due to the way libblockdev interacts with the udisk…

  • High 7.8
    CVE-2024-43583 Public exploit

    Winlogon Elevation of Privilege Vulnerability

    Winlogon Elevation of Privilege Vulnerability

  • High 7.3
    CVE-2024-22017 Public exploit

    setuid() does not affect libuv's internal io_uring operations if initialized before the call to setuid(). This allows t…

  • High 7.8
    CVE-2023-27010 Public exploit

    Wondershare Dr.Fone v12.9.6 was discovered to contain weak permissions for the service WsDrvInst. This vulnerability al…

  • High 7.0
    CVE-2019-16784 Public exploit

    Local Privilege Escalation present only on the Windows version of PyInstaller

    In PyInstaller before version 3.6, only on Windows, a local privilege escalation vulnerability is present in this particular case: If a software using PyInstaller in "onefile" mode is launched by a privileged user (at least more than the current one) which ha…