Secret disclosure via unenforced snippet restriction
Published Apr 21, 2022 · Updated Aug 3, 2024
Snippet restriction bypass in F5 NGINX Ingress Controller 1.x before 1.12.3 and 2.x before 2.0.3 allows remote authenticated users to read secrets. The Ingress validation path fails to apply the enable-snippets command-line gate, so snippet annotations enter generated NGINX configuration even when snippets are disabled. An attacker needs permission to create Ingress objects; injected NGINX directives can expose secrets available to the controller service account.
Summary
What happened
Snippet restriction bypass in F5 NGINX Ingress Controller 1.x before 1.12.3 and 2.x before 2.0.3 allows remote authenticated users to read secrets. The Ingress validation path fails to apply the enable-snippets command-line gate, so snippet annotations enter generated NGINX configuration even when snippets are disabled. An attacker needs permission to create Ingress objects; injected NGINX directives can expose secrets available to the controller service account.
The record
- CVE
- CVE-2021-23055
- Published
- Apr 21, 2022
- Updated
- Aug 3, 2024
- Vendor
- F5 Networks
- Product
- NGINX Ingress Controller
- Classifications
- CWE-732, T1552.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 21, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=2.x before 2.0.3 and 1.x before 1.12.3
What conditions does exploitation require?
What is affected?
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