Leakage of sensitive data to HoneyBadget

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

Description

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

Remediations

• Do ensure all sensitive data is removed when sending data to third-party loggers like Honeybadger.
• Do use unique identifiers from the database if you really need to identify users.

    const Honeybadger = require("@honeybadger-io/js");
  
    let context = { user: { uuid: "aacd05fd-8f5b-4bc6-aa8b-35e5fbf37325" } };
  
    Honeybadger.setContext(context);

References

• Honeybadger Docs
• 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