Authenticated command execution via configuration-snippet injection
Published Oct 25, 2023 · Updated Feb 13, 2025
Command injection in Kubernetes ingress-nginx before 1.9.0 allows remote authenticated users to execute commands through an Ingress annotation. The controller inserts the configuration-snippet value into a generated NGINX location without rejecting command-capable content. The attacker needs permission to create or update Ingress objects; successful execution can expose controller credentials and, by default, every cluster secret.
Summary
What happened
Command injection in Kubernetes ingress-nginx before 1.9.0 allows remote authenticated users to execute commands through an Ingress annotation. The controller inserts the configuration-snippet value into a generated NGINX location without rejecting command-capable content. The attacker needs permission to create or update Ingress objects; successful execution can expose controller credentials and, by default, every cluster secret.
The record
- CVE
- CVE-2023-5043
- Published
- Oct 25, 2023
- Updated
- Feb 13, 2025
- Vendor
- Kubernetes
- Product
- ingress-nginx
- Classifications
- CWE-74, CWE-20, CAPEC-233, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.9.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo