Leakage of sensitive data to Algolia

• Rule ID: javascript_third_parties_algolia
• Languages: javascript
• Source: algolia.yml

Description

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

Remediations

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

  const algoliaSearch = require('algoliasearch')
  const myAlgolia = algoliaSearch("123", "123")
  const index = myAlgolia.initIndex(user.uuid)

Resources

• Algolia 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_algolia

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

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