Insecure exceptions - Empty or no catch
Description
The application does not perform proper exception handling. Empty _catch_ statements are found, or _try_ statements without their respective _catch_. This behavior can make the application temporarily or permanently unavailable by presenting errors that are not being handled.
Impact
- Generate the crash of the application due to errors that are not being taken into account.
- Lose the traceability of the errors presented.
Recommendation
For every _try_ sentence define its respective _catch_ handling the exception accordingly.
Threat
Authenticated attacker from the Internet.
Expected Remediation Time
⌚ 40 minutes.
Score
Default score using CVSS 3.1. It may change depending on the context of the src.
Base
- Attack vector: N
- Attack complexity: H
- Privileges required: L
- User interaction: N
- Scope: U
- Confidentiality: N
- Integrity: N
- Availability: L
Temporal
- Exploit code maturity: P
- Remediation level: U
- Report confidence: C
Result
- Vector string: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:U/RC:C
- Score:
- Severity:
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: N
- Attack complexity: H
- Attack Requirements: N
- Privileges required: L
- User interaction: N
- Confidentiality (VC): N
- Integrity (VI): N
- Availability (VA): L
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
Result 4.0
- Vector string: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
- Score:
- Severity:
Requirements
Fixes
Free trial