# CVE-2022-2835: coreDNS vulnerable to Improper Restriction of Communication Channel to Intended Endpoints

> Attackers can reroute internal service calls via FQDN manipulation, potentially accessing internal resources or bypassing network controls.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2023
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-ch7v-37xg-75ph

## What is CVE-2022-2835?

CVE-2022-2835 is a medium-severity server-side request forgery vulnerability in coreDNS, published on 3 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in coreDNS. This flaw allows a malicious user to reroute internal calls to some internal services that were accessed by the FQDN in a format of <service>.<namespace>.svc.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

## Which versions are affected by CVE-2022-2835?

2 open source packages ship an affected version, including github.com/coredns/coredns. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/coredns/coredns` | Go | All versions to 1.9.3 | None |
| `github.com/coredns/coredns` | Go | All versions to 1.9.3 | None |

Products: Coredns.io Coredns.

## How do I fix CVE-2022-2835?

No fix has been published for CVE-2022-2835 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-2835 being exploited?

There is no known exploitation of CVE-2022-2835 in the wild and no public exploit code.

## Other vulnerabilities in coreDNS

- [CVE-2026-32934](https://insights.sbomify.com/CVE-2026-32934/): CoreDNS DNS-over-QUIC unbounded goroutine growth leads to denial of service (high 8.7)
- [CVE-2026-32936](https://insights.sbomify.com/CVE-2026-32936/): CoreDNS DoH GET path missing size validation causes CPU and memory amplification (high 8.7)
- [CVE-2026-33190](https://insights.sbomify.com/CVE-2026-33190/): CoreDNS TSIG authentication bypass on encrypted DNS transports (high 8.7)
- [CVE-2026-33489](https://insights.sbomify.com/CVE-2026-33489/): CoreDNS transfer plugin subzone ACL bypass via lexicographic zone comparison (high 8.2)
- [CVE-2026-35579](https://insights.sbomify.com/CVE-2026-35579/): CoreDNS TSIG authentication bypass on gRPC, QUIC, DoH, and DoH3 transports (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2835 and fix it if it is affected.

What it is: CVE-2022-2835 is a medium-severity server-side request forgery vulnerability in coreDNS, published on 3 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2835 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/coredns/coredns (Go): affected all versions up to 1.9.3; no fix listed
- github.com/coredns/coredns (Go): affected all versions up to 1.9.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2835/ (Markdown: https://insights.sbomify.com/CVE-2022-2835/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2835
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2835
- OSV: https://osv.dev/vulnerability/CVE-2022-2835

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2835/
Summaries are generated and may contain mistakes; the official description above is the record.