CVE-2018-17244: Exposure of Sensitive Information to an Unauthorized Actor in Elasticsearch

org.elasticsearch:elasticsearch Updated 02 Oct 2025

Summary

13/05/2022

Disclosed on

CVE-2018-17244

CVE

Yes i

Fix available

Moderate

Severity

6.5

CVSS Score

CVE-2018-17244: Exposure of Sensitive Information to an Unauthorized Actor in Elasticsearch. Affects org.elasticsearch:elasticsearch versions >= 6.4.0, < 6.4.3. Fixed in 6.4.3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

Elasticsearch is an open-source search and analytics engine that is widely used for various applications, including data exploration, log monitoring, and full-text search. It provides a distributed, RESTful architecture for storing and retrieving data. The vulnerability identified as CVE-2018-17244 affects Elasticsearch Security versions 6.4.0 to 6.4.2. This vulnerability arises from an error in the way request headers are applied to requests when using the Active Directory, LDAP, Native, or File realms. If the same username is being authenticated concurrently, a request may receive headers intended for another request. This can lead to the request running as the incorrect user, potentially allowing unauthorized access to sensitive information.

Vulnerability Detail

The vulnerability in Elasticsearch Security versions 6.4.0 to 6.4.2 allows an unauthorized actor to access sensitive information. When multiple requests with the same username are authenticated concurrently, request headers may be applied incorrectly, resulting in a request running as the wrong user. This can lead to unauthorized access to information that should be restricted. The vulnerability has a CVSS score of 6.5, indicating a moderate severity level. It falls under the CWE-200 category, which relates to information exposure.

How To Fix

Minimum fixed version

6.4.3

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. The recommended approach is to upgrade to the fixed version of Elasticsearch Security.

Conclusion

The vulnerability identified as CVE-2018-17244 in Elasticsearch Security versions 6.4.0 to 6.4.2 allows unauthorized access to sensitive information. It is crucial to upgrade to version 6.4.3 or later to mitigate this risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.elasticsearch:elasticsearch →