SafeTP Server 1.46 Network Address Translation IP address information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in SafeTP Server 1.46. Impacted is an unknown function of the component Network Address Translation. This manipulation causes information disclosure (IP address). This vulnerability is registered as CVE-2002-1943. Furthermore, an exploit is available.
Details
A vulnerability classified as problematic was found in SafeTP Server 1.46. Affected by this vulnerability is some unknown processing of the component Network Address Translation. The manipulation with an unknown input leads to a information disclosure vulnerability (IP Address). The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
SafeTP 1.46, when network address translation (NAT) is being used, leaks the internal IP address of the FTP server in a response to a passive mode (PASV) file transfer request.
The weakness was published 12/31/2002 (Website). The advisory is shared at online.securityfocus.com. This vulnerability is known as CVE-2002-1943 since 06/29/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (10210), Exploit-DB (21876) and SecurityFocus (BID 5822†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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
Name: IP AddressClass: Information disclosure / IP Address
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/28/2002 🔍12/31/2002 🔍
12/31/2002 🔍
06/29/2005 🔍
08/05/2014 🔍
12/29/2024 🔍
Sources
Advisory: online.securityfocus.com⛔Status: Not defined
CVE: CVE-2002-1943 (🔍)
GCVE (CVE): GCVE-0-2002-1943
GCVE (VulDB): GCVE-100-19585
X-Force: 10210
SecurityFocus: 5822 - SafeTP Passive Mode Internal IP Address Revealing Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/05/2014 11:07Updated: 12/29/2024 06:04
Changes: 08/05/2014 11:07 (43), 06/10/2018 09:09 (8), 07/06/2024 17:09 (17), 12/29/2024 06:04 (14)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.