ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2018-17244

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.

Published Dec 20, 2018 · catalog updated Jun 17, 2026 · Elasticsearch Security versions 6.4.0

Last checked Nov 4, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2018-17244. EPSS is 1.46%. Act only if a listed version of Elasticsearch Security versions 6.4.0 is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Elasticsearch Security versions 6.4.0).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.46%
Remediation
Version ranges on file
Affected products
cpe elastic/elasticsearch

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe elastic/elasticsearch>= 6.4.0, <= 6.4.2

How to fix CVE-2018-17244

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2018-17244. EPSS is 1.46%. Act only if a listed version of Elasticsearch Security versions 6.4.0 is installed.

Which versions are affected?

Compare what you have installed with >= 6.4.0, <= 6.4.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-200: Exposure of Sensitive Information; CWE-362: Race Condition. EPSS 1.46%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Elasticsearch security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Dec 20, 2018 · Monitored products — high

    Detected

    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 u

  2. Jun 17, 2026 · Monitored products — high

    Updated

    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 u

Sources

  • CVE.orgVulnerability recordCVE-2018-17244

    Official CVE identifier

    cve.org
  • Monitored products — highVendor advisoryCVE-2018-17244

    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 u

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 2, 2026
  • Monitored products — highNov 1, 2026