Skip to content
Fencer Intel
medium 5.9

CVE-2019-7614 json

Concurrent Execution using Shared Resource with Improper Synchronization in Elasticsearch

published 7y ago modified 4mo ago also GHSA-jqm6-m3j3-8gg9 , EUVD-2022-4417

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

Summary

A race condition flaw was found in the response headers Elasticsearch versions before 7.2.1 and 6.8.2 returns to a request. On a system with multiple users submitting requests, it could be possible for an attacker to gain access to response header containing sensitive data from another user.

Patch / fix

  • maven org.elasticsearch:elasticsearch 6.8.2, 7.2.1
  • elastic elasticsearch 6.8.2, 7.2.1

Is CVE-2019-7614 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-7614 updated cvss 2.0

elasticsearch: Race condition in response headers on systems with multiple submitting requests

  • Red Hat Decision Manager 7 elasticsearch
    affected: workaround, no fix available “There is no mitigation for this issue, the flaw can only be resolved by applying updates.”
  • Red Hat JBoss Fuse 6 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 Red Hat OpenShift Container Platform 3.6 elasticsearch
    +1 more products
    Red Hat OpenShift Container Platform 3.7 elasticsearch
    affected: workaround, no fix planned “There is no mitigation for this issue, the flaw can only be resolved by applying updates.”
  • 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
    affected: workaround, no fix available “There is no mitigation for this issue, the flaw can only be resolved by applying updates.”
  • Red Hat OpenShift Enterprise 3.1 elasticsearch
    affected: workaround, no fix planned “There is no mitigation for this issue, the flaw can only be resolved by applying updates.”
  • Red Hat Process Automation 7 elasticsearch
    affected: workaround, no fix available “There is no mitigation for this issue, the flaw can only be resolved by applying updates.”
  • Red Hat Fuse 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

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

CVSS scores

assigned by version score vector
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.0 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
<6.8.2
>=7.0.0, <7.2.1
6.8.2
7.2.1

Affected products

  • Elastic Elasticsearch

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

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.