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

> Attackers can poison the DNS cache by exploiting misinterpretation of special domain name characters, leading to incorrect IP address resolution.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5wg5-mm98-g4ph

## What is CVE-2022-33993?

CVE-2022-33993 is a medium-severity vulnerability in n/a, published on 15 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Misinterpretation of special domain name characters in DNRD (aka Domain Name Relay Daemon) 2.20.3 leads to cache poisoning because domain names and their associated IP addresses are cached in their misinterpreted form.

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

It affects 1 product.


Products: Domain Name Relay Daemon Project Domain Name Relay Daemon.

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

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

## Is CVE-2022-33993 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-33992](https://insights.sbomify.com/CVE-2022-33992/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33993 is a medium-severity vulnerability in n/a, published on 15 Aug 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-33993 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-33993/ (Markdown: https://insights.sbomify.com/CVE-2022-33993/index.md)
```

## Sources

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

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