# CVE-2022-30257: Other in n/a

> Attackers can resolve revoked or expired domains, bypassing security controls and maintaining access to malicious infrastructure via Technitium DNS Server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-q889-wjj8-c346

## What is CVE-2022-30257?

CVE-2022-30257 is a critical vulnerability in n/a, published on 21 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Technitium DNS Server through 8.0.2 that allows variant V1 of unintended domain name resolution. A revoked domain name can still be resolvable for a long time, including expired domains and taken-down malicious domains. The effects of an exploit would be widespread and highly impactful, because the exploitation conforms to de facto DNS specifications and operational practices, and overcomes current mitigation patches for "Ghost" domain names.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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

It affects 1 product.


Products: Technitium Dns Server.

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

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

## Is CVE-2022-30257 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30258](https://insights.sbomify.com/CVE-2022-30258/): Other in n/a (critical 9.8)
- [CVE-2022-48256](https://insights.sbomify.com/CVE-2022-48256/): Denial of service in n/a (high 7.5)
- [CVE-2021-43105](https://insights.sbomify.com/CVE-2021-43105/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30257 is a critical vulnerability in n/a, published on 21 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30257 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-30257/ (Markdown: https://insights.sbomify.com/CVE-2022-30257/index.md)
```

## Sources

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

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