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

> Attackers can poison DNS cache by predicting transaction IDs, leading to potential redirection of traffic to malicious sites.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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-xjcj-rmfc-7q3p

## What is CVE-2022-33988?

CVE-2022-33988 is a high-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

dproxy-nexgen (aka dproxy nexgen) re-uses the DNS transaction id (TXID) value from client queries, which allows attackers (able to send queries to the resolver) to conduct DNS cache-poisoning attacks because the TXID value is known to the attacker.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

It affects 1 product.


Products: Dproxy-Nexgen Project Dproxy-Nexgen.

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

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

## Is CVE-2022-33988 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-33990](https://insights.sbomify.com/CVE-2022-33990/): Other in n/a (high 7.5)
- [CVE-2022-33989](https://insights.sbomify.com/CVE-2022-33989/): Other in n/a (medium 5.3)
- [CVE-2022-33991](https://insights.sbomify.com/CVE-2022-33991/): Security feature bypass in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33988 is a high-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-33988 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-33988/ (Markdown: https://insights.sbomify.com/CVE-2022-33988/index.md)
```

## Sources

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

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