SugarCRM Sugar Sales up to 2.0.1c Installation cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in SugarCRM Sugar Sales up to 2.0.1c. Affected by this vulnerability is an unknown functionality of the component Installation. The manipulation leads to cleartext storage. This vulnerability is documented as CVE-2004-1228. There is not any exploit available.
Details
A vulnerability, which was classified as critical, has been found in SugarCRM Sugar Sales up to 2.0.1c. This issue affects some unknown processing of the component Installation. 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, and availability. The summary by CVE is:
The install scripts in SugarCRM Sugar Sales 2.0.1c and earlier are not removed after installation, which allows attackers to obtain the MySQL administrative password in cleartext from an installation form, or to cause a denial of service by changing database settings to the default.
The weakness was released 01/10/2005 by Daniel Fabian with SEC-CONSULT (Website). It is possible to read the advisory at marc.theaimsgroup.com. The identification of this vulnerability is CVE-2004-1228 since 12/14/2004. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1555 according to MITRE ATT&CK.
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 (18449) and SecurityFocus (BID 11896†). Entries connected to this vulnerability are available at VDB-23770, VDB-23769 and VDB-23768. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.5
VulDB Temp Score: 6.5
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: 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
12/13/2004 🔍12/14/2004 🔍
01/10/2005 🔍
01/10/2005 🔍
03/10/2015 🔍
07/21/2017 🔍
Sources
Advisory: marc.theaimsgroup.comResearcher: Daniel Fabian
Organization: SEC-CONSULT
Status: Not defined
CVE: CVE-2004-1228 (🔍)
GCVE (CVE): GCVE-0-2004-1228
GCVE (VulDB): GCVE-100-23771
X-Force: 18449 - Sugar Sales plaintext MySQL password
SecurityFocus: 11896 - SugarSales Multiple Remote Vulnerabilities
See also: 🔍
Entry
Created: 03/10/2015 15:27Updated: 07/21/2017 10:26
Changes: 03/10/2015 15:27 (46), 07/21/2017 10:26 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.