- What is CWE-565?
- The 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.
- What CVEs are caused by CWE-565?
- 32 recorded CVEs are attributed to CWE-565, including CVE-2026-0257, CVE-2023-41084, CVE-2014-125112. 1 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
- How do you prevent CWE-565?
- Avoid using cookie data for a security-related decision.
- How is CWE-565 detected?
- 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.)
- What are the consequences of CWE-565?
- Exploiting CWE-565 can lead to: Modify Application Data, Execute Unauthorized Code or Commands, Gain Privileges or Assume Identity.
- Is CWE-565 actively exploited?
- Yes. 1 CWE-565 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 32 recorded CVEs.