VYPR
Unrated severityNVD Advisory· Published Aug 15, 2022· Updated Aug 3, 2024

CVE-2022-34294

CVE-2022-34294

Description

totd 1.5.3 uses a fixed UDP source port in upstream queries sent to DNS resolvers. This allows DNS cache poisoning because there is not enough entropy to prevent traffic injection attacks.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Affected products

2
  • totd/totddescription
  • totd/totdllm-create
    Range: = 1.5.3

Patches

Vulnerability mechanics

Root cause

"totd uses a fixed UDP source port for all upstream DNS queries, providing insufficient entropy to prevent traffic injection attacks."

Attack vector

An attacker who controls a script or web page loaded on a client behind the vulnerable totd forwarder can trigger DNS queries from that client [ref_id=1]. Because totd uses a fixed UDP source port (port 1024) for all upstream queries, the attacker can inject spoofed DNS responses that appear to come from the upstream resolver, since the only entropy an attacker must guess is the DNS transaction ID [ref_id=1]. This enables classic Kaminsky-style DNS cache poisoning against the upstream resolver's cache [ref_id=1].

Affected code

The advisory does not specify exact function or file paths. The vulnerability exists in the totd DNS forwarder (version 1.5.3), where the upstream query logic uses a hard-coded UDP source port (port 1024 in tests) for all queries sent to DNS resolvers [ref_id=1].

What the fix does

No patch is available for totd 1.5.3, as the project is no longer maintained [ref_id=1]. The advisory recommends that users replace totd with an alternative DNS forwarder that randomizes the UDP source port per query, thereby increasing entropy and preventing traffic injection attacks [ref_id=1].

Preconditions

  • inputAttacker must be able to trigger DNS queries from a client behind the vulnerable totd forwarder (e.g., via a malicious script or web page)
  • networkAttacker must be on a network path that allows sending spoofed DNS responses appearing to originate from the upstream resolver

Reproduction

Connect a computer to the vulnerable router/forwarder and trigger multiple DNS queries. Observe the queries sent to upstream resolvers via packet capture, either on the router's Internet-facing interface or the upstream resolver's network interface. The queries captured on these interfaces have the same UDP source port (port 1024 in tests) [ref_id=1].

Generated on May 25, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

3

News mentions

0

No linked articles in our index yet.