Skip to content
Fencer Intel
medium 5.3

CVE-2019-7619 json

Exposure of Sensitive Information to an Unauthorized Actor in Elasticsearch

published 7y ago modified 4mo ago also GHSA-hxp8-r9g3-grfr , EUVD-2022-4245

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

Summary

Elasticsearch versions 7.0.0-7.3.2 and 6.7.0-6.8.3 contain a username disclosure flaw was found in the API Key service. An unauthenticated attacker could send a specially crafted request and determine if a username exists in the Elasticsearch native realm.

Patch / fix

  • maven org.elasticsearch:elasticsearch 6.8.4, 7.4.0

Is CVE-2019-7619 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-2019-7619 updated cvss 3.7

elasticsearch: Username disclosure in API Key service

  • Red Hat JBoss Fuse 6 elasticsearch
    affected: no fix planned “Out of support scope”
  • Red Hat Decision Manager 7 elasticsearch Red Hat Fuse 7 elasticsearch 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
    +8 more products
    Red Hat OpenShift Container Platform 3.6 elasticsearch Red Hat OpenShift Container Platform 3.7 elasticsearch Red Hat OpenShift Container Platform 3.9 elasticsearch Red Hat OpenShift Container Platform 3.10 elasticsearch Red Hat OpenShift Container Platform 3.11 openshift3/ose-logging-elasticsearch5 Red Hat OpenShift Container Platform 4 openshift4/ose-logging-elasticsearch5 Red Hat OpenShift Enterprise 3.1 elasticsearch Red Hat Process Automation 7 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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
>=6.7.0, <6.8.4
>=7.0.0, <7.4.0
6.8.4
7.4.0

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.