# CVE-2023-31416: Elastic Cloud on Kubernetes (ECK) secret token configuration issue

> Attackers can send anonymous requests to APM Server, allowing unauthorized data ingestion and potential data exposure in Elastic Cloud on Kubernetes deployments.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2023
- **Updated:** 9 Sep 2024
- **Also known as:** GHSA-f827-q6f2-jc9c

## What is CVE-2023-31416?

CVE-2023-31416 is a medium-severity missing authorization vulnerability in Elastic Cloud on Kubernetes, published on 26 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Secret token configuration is never applied when using ECK <2.8 with APM Server >=8.0. This could lead to anonymous requests to an APM Server being accepted and the data ingested into this APM deployment.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-31416?

It affects 1 product.


Products: Elastic Elastic Cloud on Kubernetes.

## How do I fix CVE-2023-31416?

No fix has been published for CVE-2023-31416 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-31416 being exploited?

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

## Other vulnerabilities in Elastic Cloud on Kubernetes

- [CVE-2020-7010](https://insights.sbomify.com/CVE-2020-7010/): Cryptographic Issues in ECK (high 7.5)
- [CVE-2026-72640](https://insights.sbomify.com/CVE-2026-72640/): Unintended Proxy or Intermediary in Elastic Cloud on Kubernetes Leading to Cross-Namespace Secret Disclosure (medium 6.5)
- [CVE-2026-72648](https://insights.sbomify.com/CVE-2026-72648/): Information disclosure in Eck Operator (medium 6.5)
- [CVE-2026-78609](https://insights.sbomify.com/CVE-2026-78609/): Incorrect Authorization in Elastic Cloud on Kubernetes Leading to Unauthorized Modification of Data (medium 5.4)
- [CVE-2026-78600](https://insights.sbomify.com/CVE-2026-78600/): Incomplete Cleanup in Elastic Cloud on Kubernetes Leading to Unauthorized Cross-Namespace Credential Retention (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31416 and fix it if it is affected.

What it is: CVE-2023-31416 is a medium-severity missing authorization vulnerability in Elastic Cloud on Kubernetes, published on 26 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31416 in the wild and no public exploit code.

Affected product: Elastic Cloud on Kubernetes. 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-2023-31416/ (Markdown: https://insights.sbomify.com/CVE-2023-31416/index.md)
```

## Sources

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

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