# CVE-2020-10743: Cross-site request forgery in Kibana

> An attacker can trick users into performing arbitrary actions in OpenShift's Kibana via clickjacking due to missing frame protection.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5h6f-94qc-p3v7, MINI-2frp-g33p-xw24, MINI-5m7p-mj9v-6cf5, MINI-fpxf-xgpc-f3cg, MINI-hm7w-79m8-xg5c, MINI-q6r9-9q3c-xf32, MINI-r4c9-f9wg-g3f2, MINI-v2ch-qg23-m47p, MINI-xq7c-qg65-cwr2

## What is CVE-2020-10743?

CVE-2020-10743 is a medium-severity vulnerability in Elastic Kibana, published on 2 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

It was discovered that OpenShift Container Platform's (OCP) distribution of Kibana could open in an iframe, which made it possible to intercept and manipulate requests. This flaw allows an attacker to trick a user into performing arbitrary actions in OCP's distribution of Kibana, such as clickjacking.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames), CWE-358 (Improperly Implemented Security Check for Standard)

## Which versions are affected by CVE-2020-10743?

It affects 2 products.


Products: Elastic Kibana, Redhat Openshift Container Platform.

## How do I fix CVE-2020-10743?

Apply the vendor's patch.

## Is CVE-2020-10743 being exploited?

There is no known exploitation of CVE-2020-10743 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Kibana

- [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9)
- [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9)
- [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9)
- [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10743 and fix it if it is affected.

What it is: CVE-2020-10743 is a medium-severity vulnerability in Elastic Kibana, published on 2 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-10743 in the wild and no public exploit code.

Affected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-10743/ (Markdown: https://insights.sbomify.com/CVE-2020-10743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-10743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-10743
- OSV: https://osv.dev/vulnerability/CVE-2020-10743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-10743/
Summaries are generated and may contain mistakes; the official description above is the record.