CWE-565: Reliance on Cookies without Validation and Integrity Checking
low-riskThe product relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user.
Abstraction: Base
Common Consequences
Confidentiality
→
Modify Application Data
Access Control
→
Gain Privileges or Assume Identity
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.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2023-35885 | 9.8 | 94.1% | — |
| CVE-2023-35885 | 9.8 | 94.1% | — |
| CVE-2020-7070 | 4.3 | 26.1% | — |
| CVE-2022-28113 | 7.2 | 8.8% | — |
| CVE-2008-5784 | 9.8 | 5.8% | — |
| CVE-2017-7279 | 9.8 | 4.5% | — |
| CVE-2019-7266 | 9.8 | 3.9% | — |
| CVE-2017-6896 | 8.8 | 2.5% | — |
| CVE-2024-9970 | 8.8 | 1.2% | — |
| CVE-2020-29668 | 3.7 | 1.0% | — |
2
/ 100
low-risk
Active Threat
2/50 · Minimal
Exploit Availability
0/50 · Minimal