CVE-2020-7020

Elasticsearch versions before 6.8.13 and 7.9.2 contain a document disclosure flaw when Document or Field Level Security is used. Search queries do not properly preserve security permissions when executing certain complex queries. This could result in the search disclosing the existence of documents the attacker should not be able to view. This could result in an attacker gaining additional insight into potentially sensitive indices.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2020-7020 has a CVSS score of 3.1 (Low). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.8.13, 7.9.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2020-7020? CVE-2020-7020 is a low-severity improper privilege management vulnerability in org.elasticsearch:elasticsearch (maven), affecting versions < 6.8.13. It is fixed in 6.8.13, 7.9.2. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is CVE-2020-7020? CVE-2020-7020 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.elasticsearch:elasticsearch are affected by CVE-2020-7020? org.elasticsearch:elasticsearch (maven) versions < 6.8.13 is affected.
4. Is there a fix for CVE-2020-7020? Yes. CVE-2020-7020 is fixed in 6.8.13, 7.9.2. Upgrade to this version or later.
5. Is CVE-2020-7020 exploitable, and should I be worried? Whether CVE-2020-7020 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2020-7020 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2020-7020?
   • Upgrade org.elasticsearch:elasticsearch to 6.8.13 or later
   • Upgrade org.elasticsearch:elasticsearch to 7.9.2 or later

Other vulnerabilities in org.elasticsearch:elasticsearch