This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Category:API Abuse"
m |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
==Description== | ==Description== | ||
| Line 6: | Line 4: | ||
[[Category:Vulnerability]] | [[Category:Vulnerability]] | ||
| − | |||
| − | |||
Latest revision as of 19:22, 5 April 2014
Description
An API is a contract between a caller and a callee. The most common forms of API abuse are caused by the caller failing to honor its end of this contract. For example, if a program fails to call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller abuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.
Pages in category "API Abuse"
The following 2 pages are in this category, out of 2 total.
