CWE-227 · Kategoria
7PK - API Abuse
- Status
- Szkic
- Dodano
- 19 lipca 2006
- Ostatnia zmiana
- 29 czerwca 2023
Opis
This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that involve the software using an API in a manner contrary to its intended use. According to the authors of the Seven Pernicious Kingdoms, "An API is a contract between a caller and a callee. The most common forms of API misuse occurs when the caller does not honor its end of this contract. For example, if a program does not 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 misuses 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."
Wpisy w tej grupie
- CWE-242 Use of Inherently Dangerous Function
- CWE-243 Creation of chroot Jail Without Changing Working Directory
- CWE-244 Improper Clearing of Heap Memory Before Release ('Heap Inspection')
- CWE-245 J2EE Bad Practices: Direct Management of Connections
- CWE-246 J2EE Bad Practices: Direct Use of Sockets
- CWE-248 Uncaught Exception
- CWE-250 Execution with Unnecessary Privileges
- CWE-251 Often Misused: String Management
- CWE-252 Unchecked Return Value
- CWE-558 Use of getlogin() in Multithreaded Application
Źródła
Wpis z katalogu CWE 4.20.