Leakage of Sensitive Data to ElasticSearch

Overview

• Rule ID: java_third_parties_elasticsearch

• Applicable Languages: Java

• Weakness ID: CWE-201

Description

Leaking sensitive data to third-party loggers like ElasticSearch is a common cause of data breaches.

Remediation Guidelines

• Ensure that all sensitive data is removed before sending it to third-party services like ElasticSearch.

References

• Elasticsearch docs

• 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