Vulnerabilities · 2010 · Apache
CVE-2010-2952
Apache Traffic Server vulnerability
Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does not properly choose DNS source ports and transaction IDs, and does not properly use DNS query fields to validate responses, which makes it easier for man-in-the-middle attackers to poison the internal DNS cache via a crafted response.
Affected products
Traffic Server. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Apache Traffic Server runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- secunia.com/advisories/41356 · Vendor Advisory
- securitytracker.com/id?1024417
- trafficserver.apache.org/
- www.nth-dimension.org.uk/pub/NDSA20100830.txt.asc
- www.securityfocus.com/archive/1/513598/100/0/threaded
- www.securityfocus.com/bid/43111
- exchange.xforce.ibmcloud.com/vulnerabilities/61721
- issues.apache.org/jira/browse/TS-425
- nvd.nist.gov/vuln/detail/CVE-2010-2952
- cve.org/CVERecord?id=CVE-2010-2952
More vulnerabilities in Apache products
CVE-2026-47340CVE-2026-44930CVE-2026-44618CVE-2026-44417CVE-2026-42357CVE-2026-41280CVE-2026-32967CVE-2026-32966All 2,699
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.