CWE-283: Unverified Ownership | Glexia
CWE-283 (Unverified Ownership) weakness overview with consequences, detection methods, mitigations, related CVEs and MITRE ATT&CK context.
Glexia's Take · Automated analysis
CWE-283: Unverified Ownership
Unverified Ownership represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Access Control: Gain Privileges or Assume Identity: An attacker could gain unauthorized access to system resources.
Developer Pattern
CWE-283 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Automation confidence
high confidence from CWE-283, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-283: Unverified Ownership
The product does not properly verify that a critical resource is owned by the proper entity.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- This function is part of a privileged program that takes input from users with potentially lower privileges. This code does not confirm that the process to be killed is owned by the requesting user, thus allowing an attacker to kill arbitrary processes.,This function remedies the problem by checking the owner of the process before killing it:
Remediation
- Architecture and Design,Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.