COMMON WEAKNESS ENUMERATIONDraft

CWE-282

Improper Ownership Management

The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.

Abstraction

Class

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.

Root cause

How and when does the problem arise?

Lifecycle phase

Architecture and Design

REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Risk

What does successful exploitation lead to?

Gain Privileges or Assume Identity

Affected security scopes: Access Control

Defence

How is it prevented and fixed?

Architecture and Design · Operation

Defence to apply across several lifecycle phases

Detail
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

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.)