Elastic Cloud EnterpriseApplication · Elastic
CVE-2018-3829
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 · uneditedIn Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 it was discovered that a user could scale out allocators on new hosts with an invalid roles token. An attacker with access to the previous runner ID and IP address of the coordinator-host could add a allocator to an existing ECE install to gain access to other clusters data.
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 confidenceElastic Cloud Enterprise had an authorization bypass in allocator scaling where users could add new allocators using invalid roles tokens. Attackers with knowledge of runner ID and coordinator-host IP could register malicious allocators to access data from other clusters.
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
Elastic Cloud EnterpriseApplication
< 1.1.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/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 installed ECE versionRun 'ece version' from the ECE CLI or check the Cloud UI under Platform > General Settings to find the running ECE version numberAffected if The installed version is any release prior to 1.1.4 (e.g., 1.1.3, 1.0.5, etc.)
-
Review allocator list for unknown runnersNavigate to the ECE management console, go to Infrastructure > Allocators, and examine all registered allocators. Cross-reference the runner IDs shown with your documented infrastructure inventoryAffected if Any allocator exists with a runner ID that was not explicitly registered by your admin team
-
Inspect allocator registration logsQuery the ECE coordinator logs (located in /var/log/ece/ on the coordinator nodes) for entries containing 'allocator' and 'register' or 'create' around the time of potential compromiseAffected if Log entries show allocator registrations from IP addresses outside your expected coordinator host range
-
Verify coordinator host accessCheck the IP addresses of your known coordinator hosts by running 'ece host list' from the ECE CLI and confirming these match your documented coordinator nodesAffected if Traffic or registrations were observed originating from coordinator-host IPs that do not match your documented infrastructure
You are affected if your ECE version is below 1.1.4 AND you find unauthorized allocators or suspicious registration activity in your environment
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 data1.1.4
Upgrade to ECE version 1.1.4 or later which contains proper token validation. Additionally, rotate any potentially compromised runner IDs and IP addresses of coordinator hosts.
Fix this in Elastic Cloud Enterprise
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-3829 — 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-2018-3829 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