coreDNS TLD Traffic communication channel to intended endpoints
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in coreDNS and classified as critical. This issue affects some unknown processing of the component TLD Traffic Handler. The manipulation leads to communication channel to intended endpoints. This vulnerability is documented as CVE-2022-2837. There is not any exploit available.
Details
A vulnerability was found in coreDNS (the affected version unknown). It has been rated as critical. This issue affects an unknown part of the component TLD Traffic Handler. The manipulation with an unknown input leads to a communication channel to intended endpoints vulnerability. Using CWE to declare the problem leads to CWE-923. The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A flaw was found in coreDNS. This flaw allows a malicious user to redirect traffic intended for external top-level domains (TLD) to a pod they control by creating projects and namespaces that match the TLD.
The weakness was released 03/03/2023. The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2022-2837 since 08/16/2022. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-1027). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.8
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Communication channel to intended endpointsCWE: CWE-923
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/16/2022 🔍03/03/2023 🔍
03/03/2023 🔍
07/06/2025 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
CVE: CVE-2022-2837 (🔍)
GCVE (CVE): GCVE-0-2022-2837
GCVE (VulDB): GCVE-100-222281
EUVD: 🔍
Entry
Created: 03/03/2023 17:45Updated: 07/06/2025 16:57
Changes: 03/03/2023 17:45 (35), 03/31/2023 09:08 (11), 07/06/2025 16:57 (15)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.