Leakage of sensitive data to Airbrake

Overview

  • Rule ID: javascript_third_parties_airbrake

  • Applicable Languages: Javascript

  • Weakness ID: CWE-201

Description

Leaking sensitive data to third-party loggers like Airbrake is a common cause of data leaks and can lead to data breaches.

Remediation Guidelines

  • Do ensure all sensitive data is removed when logging errors or events to Airbrake

  • Do use unique identifiers from the database if you really need to identify users.

    airbrake.notify({
      error: err,
      params: { user: user.uuid },
    })

References

Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our SAST TOOL

Last updated