Skip to main content

Traceability loss

Description

Some features of the application do not properly keep track of errors, exceptional events or critical actions on the system, hidering the detection of possible security events.

Impact

Lose the tracking of exceptional events and fail to detect potential security breaches.

Recommendation

Set alerts for errors, events and critical actions using the mechanisms available by the technology stack.

Threat

Unauthorized internal attacker.

Expected Remediation Time

⌚ 30 minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the vulnerability.

Base

  • Attack vector: N
  • Attack complexity: H
  • Privileges required: H
  • User interaction: N
  • Scope: U
  • Confidentiality: L
  • Integrity: N
  • Availability: N

Temporal

  • Exploit code madurity: P
  • Remediation level: O
  • Report confidence: C

Result

  • Vector string: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C
  • Score:
    • Base: 2.2
    • Temporal: 2.0
  • Severity:
    • Base: Low
    • Temporal: Low

Code Examples

Compliant code

The application correctly handles all possible errors and exceptions

try {
// a function that potentially throws an error
do_Something();
} catch (err) {
// this code handles exceptions
throw new Error(err);
} finally {
// this code will always be executed
return ResultMsg();
}

Non compliant code

The application has an expression that does not correctly track exceptions and errors

function do_something() {
try {
return something;
} finally {
return somethingElse;
}
//Potential uncaught error
}

Requirements

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.