LiveActive security incident?Get immediate response
CVE Record

CVE-2017-8442: Elasticsearch X-Pack Security versions 5.0.0 to 5.4.3, when enabled, can result in the Elasticsearch _nodes...

Elasticsearch X-Pack Security versions 5.0.0 to 5.4.3, when enabled, can result in the Elasticsearch _nodes API leaking sensitive configuration information, such as the paths and passphrases of SSL keys that were configured as part of an authentication realm. This could allow an authenticated Elasticsearch user to improperly view these details.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A vulnerable Elasticsearch X-Pack Security deployment could expose sensitive security configuration through the _nodes API. An authenticated Elasticsearch user might see SSL key paths and passphrases tied to authentication realms. This is not described as remote code execution, but it can weaken confidentiality and increase follow-on risk if secrets are exposed.

Executive priority

Treat this as a targeted confidentiality issue for legacy Elasticsearch environments. It should be prioritized if affected versions are still running, especially where many users have cluster access. Modern, supported deployments outside the listed version range are not shown as affected by the provided sources.

Technical view

CVE-2017-8442 affects Elasticsearch X-Pack Security 5.0.0 through 5.4.3 when X-Pack Security is enabled. The _nodes API may leak sensitive configuration values, including SSL key paths and passphrases configured for authentication realms, to an authenticated Elasticsearch user. The source maps this to CWE-402, transmission or exposure of private resources.

Likely exposure

Exposure is limited to Elasticsearch clusters running X-Pack Security versions 5.0.0 to 5.4.3 with the feature enabled. Risk is higher where non-administrative authenticated users can query _nodes or where cluster users are broad, shared, or weakly governed.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. Abuse requires an authenticated Elasticsearch user and access to the vulnerable _nodes API response. The impact is sensitive configuration disclosure, which could support later compromise if leaked passphrases remain valid.

Researcher notes

Evidence is limited to the CVE description and Elastic reference. The key research question is whether _nodes responses exposed authentication realm SSL key paths or passphrases to authenticated users. Do not assume unauthenticated access, public exploitation, or a specific patch level beyond vendor guidance.

Mitigation direction

  • Identify Elasticsearch X-Pack Security deployments on versions 5.0.0 through 5.4.3.
  • Check Elastic guidance for the supported fixed version or vendor-recommended remediation.
  • Restrict _nodes API access to trusted administrative users only.
  • Review whether exposed SSL key passphrases should be rotated.
  • Reduce unnecessary authenticated Elasticsearch accounts and shared credentials.

Validation and detection

  • Confirm Elasticsearch and X-Pack Security versions on each cluster.
  • Verify whether X-Pack Security is enabled on affected clusters.
  • Review roles to identify users permitted to access _nodes output.
  • Check audit logs for _nodes API access by non-administrative users.
  • Compare current configuration against Elastic security guidance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-402: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-8442 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ElasticElasticsearch X-Pack Security5.0.0 to 5.4.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-402 · source CWE mapping

Transmission of Private Resources into a New Sphere ('Resource Leak')

Transmission of Private Resources into a New Sphere ('Resource Leak') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.