Project Purple AutoDNS 0.0.4 Domain Name autodns.pl Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Project Purple AutoDNS 0.0.4. This impacts an unknown function of the file autodns.pl of the component Domain Name Handler. Performing a manipulation results in Remote Code Execution. This vulnerability is reported as CVE-2001-1364. No exploit exists.
Details
A vulnerability classified as critical has been found in Project Purple AutoDNS 0.0.4 (Project Management Software). This affects some unknown processing of the file autodns.pl of the component Domain Name Handler. The manipulation with an unknown input leads to a remote code execution vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Vulnerability in autodns.pl for AutoDNS before 0.0.4 related to domain names that are not fully qualified.
The weakness was disclosed 07/19/2001 (Website). The advisory is shared at archives.neohapsis.com. This vulnerability is uniquely identified as CVE-2001-1364. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-17033, VDB-17038 and VDB-17040 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: Remote Code ExecutionCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/19/2001 🔍07/19/2001 🔍
07/07/2014 🔍
05/31/2018 🔍
Sources
Advisory: archives.neohapsis.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2001-1364 (🔍)
GCVE (CVE): GCVE-0-2001-1364
GCVE (VulDB): GCVE-100-17037
See also: 🔍
Entry
Created: 07/07/2014 15:15Updated: 05/31/2018 10:27
Changes: 07/07/2014 15:15 (43), 05/31/2018 10:27 (6)
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.