CAPEC-2: Inducing Account Lockout
Description
Extended Description
When the third party web server receives the crafted request and notes the error it then creates an error message that echoes the malformed message, including the exploit. Doing this converts the exploit portion of the message into to valid language elements that are executed by the viewing browser. When a victim executes the query provided by the adversary the infected error message is returned including the exploit code which then runs in the victim's browser. XSS can result in execution of code as well as data leakage (e.g. session cookies can be sent to the attacker). This type of attack is especially dangerous since the exploit appears to come from the third party web server, who the victim may trust and hence be more vulnerable to deception.
Severity :
Medium
Possibility :
High
Type :
Standard
Relationships with other CAPECs
This table shows the other attack patterns and high level categories that are related to this attack pattern.
Prerequisites
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- The system has a lockout mechanism.
- An attacker must be able to reproduce behavior that would result in an account being locked.
Skills required
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- Low No programming skills or computer knowledge is needed. An attacker can easily use this attack pattern following the Execution Flow above.
Taxonomy mappings
Mappings to ATT&CK, OWASP and other frameworks.
Resources required
Computer with access to the login portion of the target system
Related CWE
A Related Weakness relationship associates a weakness with this attack pattern. Each association implies a weakness that must exist for a given attack to be successful.
Visit http://capec.mitre.org/ for more details.