2322
Nature Type ID Name Page
MemberOf 699 Software Development 699 2555
HasMember 364 Signal Handler Race Condition 699 899
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name
PLOVER Signal Errors
Notes
Maintenance
Several weaknesses could exist, but this needs more study. Some weaknesses might be
unhandled signals, untrusted signals, and sending the wrong signals.
Category-388: 7PK - Errors
Category ID : 388
Summary
This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability
classification. It includes weaknesses that occur when an application does not properly handle
errors that occur during processing. According to the authors of the Seven Pernicious Kingdoms,
"Errors and error handling represent a class of API. Errors related to error handling are so common
that they deserve a special kingdom of their own. As with 'API Abuse,' there are two ways to
introduce an error-related security vulnerability: the most common one is handling errors poorly (or
not at all). The second is producing errors that either give out too much information (to possible
attackers) or are difficult to handle."
Membership
Nature Type ID Name Page
MemberOf 700 Seven Pernicious Kingdoms 700 2557
HasMember 391 Unchecked Error Condition 700 948
HasMember 395 Use of NullPointerException Catch to Detect NULL
Pointer Dereference
700 957
HasMember 396 Declaration of Catch for Generic Exception 700 959
HasMember 397 Declaration of Throws for Generic Exception 700 961
References
[REF-6]Katrina Tsipenyuk, Brian Chess and Gary McGraw. "Seven Pernicious Kingdoms: A
Taxonomy of Software Security Errors". NIST Workshop on Software Security Assurance Tools
Techniques and Metrics. 2005 November 7. NIST. < https://samate.nist.gov/SSATTM_Content/
papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security
%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf >.
Category-389: Error Conditions, Return Values, Status Codes
Category ID : 389
Summary
This category includes weaknesses that occur if a function does not generate the correct return/
status code, or if the application does not handle all possible return/status codes that could be
generated by a function. This type of problem is most often found in conditions that are rarely
CWE Version 4.14
CWE-398: 7PK - Code Quality
CWE-398: 7PK - Code Quality