Leakage of sensitive data to Algolia

Overview

• Rule ID: javascript_third_parties_algolia

• Applicable Languages: Javascript

• Weakness ID: CWE-201

Description

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

Remediation Guidelines

• Do ensure all sensitive data is removed when logging errors or events to Algolia

• Do use unique identifiers from the database if you really need to identify users.

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

References

• Algolia docs

• OWASP logging cheat sheet

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

• OWASP Top 10: A01:2021 - Broken Access Control

Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our SAST TOOL