678
Mapped Taxonomy Name Node ID Fit Mapped Node Name
PLOVER Ownership errors
Related Attack Patterns
CAPEC-ID Attack Pattern Name
17 Using Malicious Files
35 Leverage Executable Code in Non-Executable Files
CWE-283: Unverified Ownership
Weakness ID : 283
Structure : Simple
Abstraction : Base
Description
The product does not properly verify that a critical resource is owned by the proper entity.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 282 Improper Ownership Management 676
Relevant to the view "Architectural Concepts" (CWE-1008)
Nature Type ID Name Page
MemberOf 1011 Authorize Actors 2425
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 840 Business Logic Errors 2360
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Access Control Gain Privileges or Assume Identity
An attacker could gain unauthorized access to system
resources.
Potential Mitigations
Phase: Architecture and Design
Phase: Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage
trust zones in the software.
Phase: Architecture and Design
Strategy = Separation of Privilege
CWE Version 4.14
CWE-283: Unverified Ownership
CWE-283: Unverified Ownership