Leakage of sensitive data to HoneyBadget

• Rule ID: javascript_third_parties_honeybadger
• Languages: javascript
• Source: honeybadger.yml

Description

Leaking sensitive data to third-party error logging tools is a common cause of data leaks and can lead to data breaches. This rule looks for instances of sensitive data sent to Honeybadger.

Remediations

When sending data to logging libraries, ensure all sensitive data is removed.

If you really need to identify users, use unique identifiers from the database.

  const Honeybadger = require("@honeybadger-io/js");

  let context = { user: { uuid: "aacd05fd-8f5b-4bc6-aa8b-35e5fbf37325" } };

  Honeybadger.setContext(context);

Resources

• OWASP logging cheat sheet

Associated CWE

• CWE-201: Insertion of Sensitive Information Into Sent Data

OWASP Top 10

• A01:2021 - Broken Access Control

Configuration

To skip this rule during a scan, use the following flag

bearer scan /path/to/your-project/ --skip-rule=javascript_third_parties_honeybadger

To run only this rule during a scan, use the following flag

bearer scan /path/to/your-project/ --only-rule=javascript_third_parties_honeybadger