Leakage of sensitive data to Bugsnag

• Rule ID: javascript_third_parties_bugsnag
• Languages: javascript
• Source: bugsnag.yml

Description

Leaking sensitive data to third-party loggers like Bugsnag 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 Bugsnag.
• Do use unique identifiers from the database if you really need to identify users.

    import { Bugsnag } from "@bugsnag/js"
  
    var bugSession = Bugsnag.startSession()
    bugSession.notify(user.uuid)

References

• Bugsnag 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_bugsnag

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

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