| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Apache Traffic Server. Affected by this issue is some unknown functionality of the component DNS Cache. Performing a manipulation results in input validation. This vulnerability was named CVE-2010-2952. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Apache Traffic Server. This affects some unknown functionality of the component DNS Cache. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on integrity. The summary by CVE is:
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.
The weakness was presented 09/13/2010 by Tim Brown with Nth Dimension (Website). The advisory is shared at issues.apache.org. This vulnerability is uniquely identified as CVE-2010-2952 since 08/04/2010. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.0.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (61721), SecurityFocus (BID 43111†), Secunia (SA41356†) and SecurityTracker (ID 1024417†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 100797
OpenVAS Name: Apache Traffic Server Remote DNS Cache Poisoning Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Traffic Server 2.0.0
Timeline
08/04/2010 🔍09/09/2010 🔍
09/09/2010 🔍
09/10/2010 🔍
09/13/2010 🔍
09/13/2010 🔍
03/19/2015 🔍
01/07/2018 🔍
Sources
Vendor: apache.orgAdvisory: issues.apache.org
Researcher: Tim Brown
Organization: Nth Dimension
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2010-2952 (🔍)
GCVE (CVE): GCVE-0-2010-2952
GCVE (VulDB): GCVE-100-54693
X-Force: 61721 - Apache Traffic Server cache poisoning
SecurityFocus: 43111 - Apache Traffic Server Remote DNS Cache Poisoning Vulnerability
Secunia: 41356 - Apache Traffic Server DNS Cache Poisoning Vulnerability, Less Critical
SecurityTracker: 1024417
Entry
Created: 03/19/2015 14:37Updated: 01/07/2018 11:14
Changes: 03/19/2015 14:37 (58), 01/07/2018 11:14 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.

No comments yet. Languages: en.
Please log in to comment.