CAPEC-22: Exploiting Trust in Client
Description
Extended Description
By observing logs and error messages, the attacker can learn details about the configuration of the target application and might be able to cause the target to disclose sensitive information. In applications that return a stack trace along with the error, this can enumerate the chain of methods that led up to the point where the error was encountered. This can not only reveal the names of the methods (some of which may have known weaknesses) but possibly also the location of class files and libraries as well as parameter values. In some cases, the stack trace might even disclose sensitive configuration or user information.
Severity :
High
Possibility :
High
Type :
Meta
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.
- Server software must rely on client side formatted and validated values, and not reinforce these checks on the server side.
Skills required
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- Medium The attacker must have fairly detailed knowledge of the syntax and semantics of client/server communications protocols and grammars
Taxonomy mappings
Mappings to ATT&CK, OWASP and other frameworks.
Resources required
Ability to communicate synchronously or asynchronously with server
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.