CVE-2010-2952
Published Sep 13, 2010 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
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.
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- 43111 ↗
- issues.apache.org ↗
- 41356 ↗
- www.nth-dimension.org.uk ↗
- apache-traffic-cache-poisoing(61721) ↗
- 1024417 ↗
- trafficserver.apache.org ↗
- 20100908 Medium security flaw in Apache Traffic Server ↗
Record history
Published Sep 13, 2010 · Last refreshed Nov 3, 2026