Elastic Cloud EnterpriseApplication · Elastic
CVE-2024-37282
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 · uneditedIt was identified that under certain specific preconditions, an API key that was originally created with a specific privileges could be subsequently used to create new API keys that have elevated privileges.
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 · moderate confidenceA privilege escalation vulnerability in API key management allows an API key with limited privileges to be used to create new API keys with elevated/higher privileges, bypassing intended authorization controls.
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
>= 3.0.0, < 3.7.2CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Elastic Cloud Enterprise installation and versionRun 'ece version' or check the administration console to determine the installed Elastic Cloud Enterprise versionAffected if The installed version is greater than or equal to 3.0.0 and less than 3.7.2
-
Verify API key management is in useCheck if API keys are being created or managed within the Elastic Cloud Enterprise environment through the API or UIAffected if API key management features are actively used and the version falls within the affected range
-
Review API key creation logsExamine Elastic Cloud Enterprise audit logs for API key creation events, specifically looking for cases where an API key with lower privileges created a key with higher privilegesAffected if Logs show API keys with limited privileges successfully creating new keys with elevated or higher-level permissions
You are affected if Elastic Cloud Enterprise version 3.0.0 through 3.7.2 is installed and API key management is in use, with any evidence of limited-privilege keys creating elevated-privilege keys.
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.
dbcve · scoped3.7.2
Implement strict validation that the requesting API key's privileges are verified against the requested privileges for any new key creation, ensuring users cannot escalate their own permissions beyond what they were originally granted.
Elastic Cloud Enterprise 3.7.2 or later
- Upgrade Elastic Cloud Enterprise to version 3.7.2 or later
- After upgrade, audit existing API keys to ensure no unauthorized elevated keys were created
- Verify the upgrade was successful by checking the Elastic Cloud Enterprise version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Elastic Cloud Enterprise
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-2024-37282 — 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-2024-37282 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