Skip to content
Fencer Intel
high 8.8

CVE-2018-3831 json

Exposure of Sensitive Information to an Unauthorized Actor in Elasticsearch

published 8y ago modified 4mo ago also GHSA-r9fv-qpm9-rj4g , EUVD-2022-5136

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue when secrets are configured via the API. The Elasticsearch _cluster/settings API, when queried, could leak sensitive configuration information such as passwords, tokens, or usernames. This could allow an authenticated Elasticsearch user to improperly view these details.

Patch / fix

  • maven org.elasticsearch:elasticsearch 5.6.12, 6.4.1
  • elastic elasticsearch 5.6.12, 6.4.1

Is CVE-2018-3831 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-3831 updated cvss 5.3

elasticsearch: Information exposure via _cluster/settings API

  • Red Hat Decision Manager 7 elasticsearch
    affected: no fix available
  • Red Hat JBoss Fuse 6 elasticsearch
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 8 (Liberty) Operational Tools elasticsearch Red Hat OpenStack Platform 9 (Mitaka) Operational Tools elasticsearch
    affected: no fix planned “Will not fix”
  • Red Hat Process Automation 7 elasticsearch
    affected: no fix available
  • Red Hat Subscription Asset Manager elasticsearch
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7.7.0
    fixed: vendor fix RHSA-2020:3192
  • Red Hat OpenShift Container Platform 3.2 elasticsearch Red Hat OpenShift Container Platform 3.3 elasticsearch Red Hat OpenShift Container Platform 3.4 elasticsearch Red Hat OpenShift Container Platform 3.5 elasticsearch Red Hat OpenShift Container Platform 3.6 elasticsearch Red Hat OpenShift Container Platform 3.7 elasticsearch
    +5 more products
    Red Hat OpenShift Container Platform 3.9 elasticsearch Red Hat OpenShift Container Platform 3.10 elasticsearch Red Hat OpenShift Container Platform 3.11 elasticsearch Red Hat OpenShift Enterprise 3.0 elasticsearch Red Hat OpenShift Enterprise 3.1 elasticsearch
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.99% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
>=5.6.0, <5.6.12
>=6.0.0, <6.4.1
5.6.12
6.4.1

Affected products

  • Elastic Elasticsearch

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.