Описание
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.
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2010-2952
- https://exchange.xforce.ibmcloud.com/vulnerabilities/61721
- https://issues.apache.org/jira/browse/TS-425
- http://secunia.com/advisories/41356
- http://securitytracker.com/id?1024417
- http://trafficserver.apache.org
- http://www.nth-dimension.org.uk/pub/NDSA20100830.txt.asc
- http://www.securityfocus.com/archive/1/513598/100/0/threaded
- http://www.securityfocus.com/bid/43111
Связанные уязвимости
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.
Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, d ...