Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does...
Vulnerability Description
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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2010-2952
Credits & Attribution
No credits recorded in the NVD database.
References
- http://www.securityfocus.com/bid/43111
- https://issues.apache.org/jira/browse/TS-425
- http://secunia.com/advisories/41356
- http://www.nth-dimension.org.uk/pub/NDSA20100830.txt.asc
- https://exchange.xforce.ibmcloud.com/vulnerabilities/61721
- http://securitytracker.com/id?1024417
- http://trafficserver.apache.org/
- http://www.securityfocus.com/archive/1/513598/100/0/threaded
More from apache
View All →Affected Vendor
apache
View all reports →Affected Software
Timeline
CVSS Vectors
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.