962
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 221 Information Loss or Omission 556
ChildOf 703 Improper Check or Handling of Exceptional Conditions 1535
ChildOf 705 Incorrect Control Flow Scoping 1542
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 389 Error Conditions, Return Values, Status Codes 2322
Applicable Platforms
Language : C++ (Prevalence = Undetermined)
Language : Java (Prevalence = Undetermined)
Language : C# (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Non-Repudiation
Other
Hide Activities
Alter Execution Logic
Detection Methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST),
can find some instances of this weakness by analyzing source code (or binary/compiled code)
without having to execute it. Typically, this is done by building a model of data flow and control
flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input)
with "sinks" (destinations where the data interacts with external components, a lower layer such
as the OS, etc.)
Effectiveness = High
Demonstrative Examples
Example 1:
The following method throws three types of exceptions.
Example Language: Java (Good)
public void doExchange() throws IOException, InvocationTargetException, SQLException {
...
}
While it might seem tidier to write
Example Language: (Bad)
public void doExchange() throws Exception {
...
}
CWE Version 4.14
CWE-397: Declaration of Throws for Generic Exception
CWE-397: Declaration of Throws for Generic Exception