Local internal-service redirection via ambiguous DNS names
Published Mar 3, 2023 · Updated Mar 7, 2025
DNS redirection in CoreDNS with Kubernetes allows local users to reroute calls made to internal services through three-label service names. The public record attributes the condition to handling service.namespace.svc names but does not identify a CoreDNS function or code path that performs the wrong operation. Exploitation requires low-privileged access capable of creating conflicting Kubernetes naming state, and the bounded impact is redirection of internal service traffic.
Summary
What happened
DNS redirection in CoreDNS with Kubernetes allows local users to reroute calls made to internal services through three-label service names. The public record attributes the condition to handling service.namespace.svc names but does not identify a CoreDNS function or code path that performs the wrong operation. Exploitation requires low-privileged access capable of creating conflicting Kubernetes naming state, and the bounded impact is redirection of internal service traffic.
The record
- CVE
- CVE-2022-2835
- Published
- Mar 3, 2023
- Updated
- Mar 7, 2025
- Vendor
- CoreDNS
- Product
- CoreDNS
- Classifications
- CWE-923, T1557
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2023CVE publishedPublication date reported by the CVE source.
- Mar 7, 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=unknown
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