cve.bz

CVE-2020-7009 elastic elasticsearch: Improper Privilege Management

8.8 highEPSS 1.9%Fix available

High (8.8) in elastic elasticsearch. EPSS 1.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.elasticsearch:elasticsearch 6.8.8, 7.6.2.

On this page
Elasticsearch versions from 6.7.0 before 6.8.8 and 7.0.0 before 7.6.2 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.9% (unchanged from 1.9% a week ago; 1.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 80th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-269 Improper Privilege Management
CWE-266 Incorrect Privilege Assignment
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-7009 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-7009?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-7009?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-7009 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
elastic:elasticsearchfrom 6.7.0 before 6.8.8
elastic:elasticsearchfrom 7.0.0 before 7.6.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-gfv5-grx2-9jw2Mavenorg.elasticsearch:elasticsearch>=6.7.0 <6.8.86.8.8
GHSA-gfv5-grx2-9jw2Mavenorg.elasticsearch:elasticsearch>=7.0.0 <7.6.27.6.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu16.04:LTSelasticsearchno fix listedUBUNTU-CVE-2020-7009

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

OpenShift Container Platform 4.x and 3.11 use Elasticsearch 5.6 which does not have the API Keys feature.

ProductPackageStateAdvisory
Red Hat Decision Manager 7elasticsearchNot affected
Red Hat Fuse 7elasticsearchNot affected
Red Hat JBoss Fuse 6elasticsearchNot affected
Red Hat OpenShift Container Platform 3.11elasticsearchNot affected
Red Hat OpenShift Container Platform 4elasticsearchNot affected
Red Hat Process Automation 7elasticsearchNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2020-7009.

Attack patterns (CAPEC)

  • CAPEC-58 Restful Privilege Elevation Likelihood: High · Severity: High
  • CAPEC-122 Privilege Abuse Likelihood: High · Severity: Medium
  • CAPEC-233 Privilege Escalation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON