CVE-2018-17244

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure.

Exploit odds

1.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-12-20 22:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:45 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.5% in the next 30 days (EPSS).
• Severity: 6.5 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-12-20 22:29 UTC

Last modified

2026-06-17 01:45 UTC

Exploit probability

1.5% · EPSS, next 30 days

Weakness

CWE-362 · Race condition

Record status

Modified

Affected

• Elastic Elasticsearch ≤ 6.4.2

Attack profile CVSS 3.0 · 6.5

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2018-17244.md and follow it. Check whether this project is affected by CVE-2018-17244. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge