Leakage of sensitive data to Google Analytics

• Rule ID: javascript_third_parties_google_analytics
• Languages: javascript
• Source: google_analytics.yml

Description

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

    gtag("event", "screen_view", {
      user: {
        subscribed: true,
      },
    });

References

• Google Analytics 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_google_analytics

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

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