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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
Which versions are affected by CVE-2023-31416?
It affects 1 product.
Products include 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.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
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 Cryptographic Issues in ECK
- CVE-2026-72640 Unintended Proxy or Intermediary in Elastic Cloud on Kubernetes Leading to Cross-Namespace Secret Disclosure
- CVE-2026-72648 Information disclosure in Eck Operator
- CVE-2026-78609 Incorrect Authorization in Elastic Cloud on Kubernetes Leading to Unauthorized Modification of Data
- CVE-2026-78600 Incomplete Cleanup in Elastic Cloud on Kubernetes Leading to Unauthorized Cross-Namespace Credential Retention
Sources
Also known as GHSA-f827-q6f2-jc9c.