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

Medium 6.5 Published Updated

Concurrent authentication requests may leak headers, allowing users to access unauthorized data or run as incorrect users in Elasticsearch.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2018-17244?

CVE-2018-17244 is a medium-severity vulnerability in Elastic Elasticsearch, published on 20 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Elasticsearch Security versions 6.4.0 to 6.4.2 contain an error in the way request headers are applied to requests when using the Active Directory, LDAP, Native, or File realms. A request may receive headers intended for another request if the same username is being authenticated concurrently; when used with run as, this can result in the request running as the incorrect user. This could allow a user to access information that they should not have access to.

Weakness: CWE-200, CWE-362

Which versions are affected by CVE-2018-17244?

2 open source packages ship an affected version, including org.elasticsearch:elasticsearch. It affects 1 product.

PackageAffectedFixed in
org.elasticsearch:elasticsearch MavenFrom 6.4.06.4.3
org.elasticsearch:elasticsearch MavenFrom 6.4.06.4.3

Products include Elastic Elasticsearch.

How do I fix CVE-2018-17244?

Upgrade org.elasticsearch:elasticsearch to 6.4.3 or later.

Is CVE-2018-17244 being exploited?

There is no known exploitation of CVE-2018-17244 in the wild and no public exploit code.

All Elastic Elasticsearch vulnerabilities

Sources

Also known as GHSA-vpqm-88c4-x4cv.

Is CVE-2018-17244 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free