fix(weaver): improper exception handling #2767
Labels
good-first-issue
Good for newcomers
good-first-issue-200-intermediate
Hacktoberfest
Hacktoberfest participants are welcome to take a stab at issues marked with this label.
Security
Related to existing or potential security vulnerabilities
Weaver
Tasks related to the future of Cactus & Weaver together.
Description
Static source code assessment has picked up a potential vulnerability regarding improper exception handling. The possible remediation for the same is to have it enclosed within a try catch block and handle the exceptions accordingly.
The report from which the above information was summarized
Risk Rating: Low
Category: Security Misconfiguration
Description
The application performs some operation, such as database or file access, that could throw an exception. Since the application is not designed to properly handle the exception, the application could crash.
Impact
An attacker could maliciously cause an exception that could crash the application, potentially resulting in a denial of service (DoS) or unexpected behavior under certain erroneous conditions. Exceptions may also occur without any malicious intervention, resulting in general instability.
Remediation Recommendation
Any method that could cause an exception should be wrapped in a try-catch block that:
• Explicitly handles expected exceptions.
• Includes a default solution to explicitly handle unexpected exceptions.
Affected files (path - line number)
weaver/sdks/corda/src/main/kotlin/org/hyperledger/cacti/weaver/sdk/corda/CredentialsExtractor.java - 294,295
Snapshot of the sourcecode at the time of scan
Source:
APP PE Hyperledger Cacti v2.0.0 - Static Application Assessment Report.odt
cc: @takeutak @izuru0 @outSH @petermetz
The text was updated successfully, but these errors were encountered: