CVE-2010-2952: Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does not properly choose DNS source po...

Security readout for executives and security teams

Older Apache Traffic Server releases could be tricked into caching false DNS answers. If an attacker can interfere with DNS traffic, they may redirect Traffic Server’s internal lookups, potentially sending users or backend requests to the wrong destination. Exposure is most likely where legacy Apache Traffic Server versions from the affected ranges still operate as caching proxies or reverse proxies and perform DNS resolution over networks an attacker could observe or interfere with. Treat this as a legacy infrastructure cleanup item unless affected systems are internet-facing or use exposed DNS paths. Priority increases if Traffic Server handles sensitive routing, authentication flows, or backend service discovery. Mitigation focus: Identify any Apache Traffic Server deployments and record exact versions.; Upgrade affected 2.0.x deployments to 2.0.1 or later vendor-supported releases.; Upgrade affected 2.1.x deployments to 2.1.2-unstable or later vendor-supported releases..

Prepared

Jun 28, 2026, 01:40 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.