The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.
N/A
Threat Mapped score: 0.0
Industry: Finiancial
Threat priority: Unclassified
CVE: CVE-2002-0367 — KEV
DebPloit
CVE: CVE-2004-0261
Web auth
CVE: CVE-2002-1730
Authentication bypass by setting certain cookies to "true".
CVE: CVE-2002-1734
Authentication bypass by setting certain cookies to "true".
CVE: CVE-2002-2064
Admin access by setting a cookie.
CVE: CVE-2002-2054
Gain privileges by setting cookie.
CVE: CVE-2004-1611
Product trusts authentication information in cookie.
CVE: CVE-2005-1708
Authentication bypass by setting admin-testing variable to true.
CVE: CVE-2005-1787
Bypass auth and gain privileges by setting a variable.
Phase | Note |
---|---|
Architecture and Design | COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic. |
Implementation | N/A |
Intro: In the following example, an "authenticated" cookie is used to determine whether or not a user should be granted access to a system.
Body: Modifying the value of a cookie on the client-side is trivial, but many developers assume that cookies are essentially immutable.
boolean authenticated = new Boolean(getCookieValue("authenticated")).booleanValue(); if (authenticated) { ... }