ElasticsearchDatabase / datastore · Elastic
CVE-2019-7614
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA race condition in Elasticsearch versions before 7.2.1 and 6.8.2 allows one user to receive response headers containing sensitive data from another user's request when multiple users submit requests simultaneously.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ElasticsearchDatabase / datastore
< 6.8.2>= 7.0.0, < 7.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Elasticsearch versionRun `curl -s -XGET 'localhost:9200/'` or check the installed package version using your package manager (dpkg -r, rpm -qi, etc.)Affected if The version is less than 6.8.2 for 6.x releases OR less than 7.2.1 for 7.x releases (including 7.0.0 through 7.2.0)
-
Verify Elasticsearch service is runningCheck that Elasticsearch is actively running (systemctl status elasticsearch, ps aux | grep elasticsearch, or curl to localhost:9200 returns a response)Affected if The service is running and accessible to multiple users or applications
-
Identify if multi-user access is enabledReview Elasticsearch security configuration and cluster access settings to determine if multiple users or applications can submit requests simultaneouslyAffected if More than one user or application has authenticated access to submit requests to the cluster
-
Confirm the race condition scenario is possibleCheck if the cluster handles concurrent requests from different users (review access logs, authentication settings, and whether X-Pack Security or Shield is configured for multi-user isolation)Affected if Multiple users can submit simultaneous requests and the installed version falls within the affected range
You are affected if your Elasticsearch version is 6.x before 6.8.2 or 7.x between 7.0.0 and 7.2.0, and your cluster accepts simultaneous requests from multiple users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data6.8.27.2.1
Upgrade Elasticsearch to version 7.2.1 or later (for 7.x) or 6.8.2 or later (for 6.x) to patch the race condition vulnerability in response header handling.
Fix this in Elasticsearch
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-7614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data