1653
Relevant to the view "Weaknesses for Simplified Mapping of Published
Vulnerabilities" (CWE-1003)
Nature Type ID Name Page
ChildOf 669 Incorrect Resource Transfer Between Spheres 1471
Relevant to the view "Architectural Concepts" (CWE-1008)
Nature Type ID Name Page
MemberOf 1020 Verify Message Integrity 2434
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 1214 Data Integrity Issues 2477
Common Consequences
Scope Impact Likelihood
Access Control Gain Privileges or Assume Identity
It is dangerous to use cookies to set a user's privileges.
The cookie can be manipulated to escalate an attacker's
privileges to an administrative level.
Detection Methods
Automated Static Analysis
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.)
CWE Version 4.14
CWE-565: Reliance on Cookies without Validation and Integrity Checking
CWE-565: Reliance on Cookies without Validation and Integrity Checking