Conti FTPServer 1.0 Build 2.8 myserversettings.ini cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Conti FTPServer 1.0 Build 2.8. This issue affects some unknown processing of the file myserversettings.ini. The manipulation leads to cleartext storage. This vulnerability is uniquely identified as CVE-2006-6949. No exploit exists.
Details
A vulnerability was found in Conti FTPServer 1.0 Build 2.8. It has been rated as problematic. This issue affects an unknown code of the file myserversettings.ini. The manipulation with an unknown input leads to a cleartext storage vulnerability. Using CWE to declare the problem leads to CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Conti FTPServer 1.0 Build 2.8 stores user passwords in cleartext in MyServerSettings.ini, which allows local users to obtain sensitive information by reading this file.
The weakness was disclosed 01/22/2007 by Greg Linares (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2006-6949 since 01/22/2007. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1555 for this issue.
It is declared as proof-of-concept. By approaching the search of inurl:myserversettings.ini it is possible to find vulnerable targets with Google Hacking.
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 (30412), SecurityFocus (BID 21174†) and Secunia (SA23030†). The entry VDB-34578 is pretty similar. 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.9VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.9
VulDB Temp Score: 5.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: Cleartext storageCWE: CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍
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
11/18/2006 🔍11/19/2006 🔍
01/22/2007 🔍
01/22/2007 🔍
01/22/2007 🔍
03/13/2015 🔍
08/17/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Greg Linares
Status: Not defined
CVE: CVE-2006-6949 (🔍)
GCVE (CVE): GCVE-0-2006-6949
GCVE (VulDB): GCVE-100-34577
X-Force: 30412
SecurityFocus: 21174 - Conti FTP Insecure Default Accounts and Directory Traversal Vulnerabilities
Secunia: 23030 - Conti FTPServer Two Vulnerabilities, Less Critical
Vupen: ADV-2006-4605
See also: 🔍
Entry
Created: 03/13/2015 10:40Updated: 08/17/2018 07:19
Changes: 03/13/2015 10:40 (51), 08/17/2018 07:19 (7)
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.