Skip to content

287

cwe.mitre.org • August 19, 2026

Read Application Data; Gain Privileges or Assume Identity; Execute Unauthorized Code or Commands

Architecture and Design

Strategy: Libraries or Frameworks

Class: Not Language-Specific (Undetermined Prevalence)

Class: Not OS-Specific (Undetermined Prevalence)

Class: Not Technology-Specific (Undetermined Prevalence)

Class: Web Based (Undetermined Prevalence)

Class: ICS/OT (Often Prevalent)

The following code intends to ensure that the user is already logged in. If not, the code performs authentication with the user-provided username and password. If successful, it sets the loggedin and user cookies to "remember" that the user has already logged in. Finally, the code performs administrator tasks if the logged-in user has the "Administrator" username, as recorded in the user cookie.

Unfortunately, this code can be bypassed. The attacker can set the cookies independently so that the code does not check the username and password. The attacker could do this with an HTTP request containing headers such as:

In January 2009, an attacker was able to gain administrator access to a Twitter server because the server did not restrict the number of login attempts [ REF-236 ]. The attacker targeted a member of Twitter's support team and was able to successfully guess the member's password using a brute force attack by guessing a large number of common words. After gaining access as the member of the support staff, the attacker used the administrator panel to gain access to 33 accounts that belonged to celebrities and politicians. Ultimately, fake Twitter messages were sent that appeared to come from the compromised accounts.

In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [ REF-1283 ]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.

Multiple vendors did not use any authentication or used client-side authentication for critical functionality in their OT products.

Note: this is a curated list of examples for users to understand the variety of ways in which this weakness can be introduced. It is not a complete list of all CVEs that are related to this CWE entry.