Cutephp CuteNews up to 1.3.6 users.db.php Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Cutephp CuteNews 0.88/1.3/1.3.1/1.3.2/1.3.6. It has been classified as problematic. The affected element is an unknown function of the file users.db.php. The manipulation leads to Local Privilege Escalation. This vulnerability is listed as CVE-2004-1573. There is no available exploit.
Details
A vulnerability, which was classified as critical, has been found in Cutephp CuteNews 0.88/1.3/1.3.1/1.3.2/1.3.6 (Content Management System). This issue affects an unknown code block of the file users.db.php. The manipulation with an unknown input leads to a local privilege escalation vulnerability. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The documentation for AJ-Fork 167 implies that users should set permissions for users.db.php to 777, which allows local users to execute arbitrary PHP code and gain privileges as the administrator.
The bug was discovered 09/30/2004. The weakness was presented 12/31/2004 by Ahmad Muammar (y3dips) (Website). The advisory is shared at marc.info. The identification of this vulnerability is CVE-2004-1573 since 02/20/2005. 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.
The vulnerability was handled as a non-public zero-day exploit for at least 92 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:users.db.php 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 (17571), SecurityFocus (BID 11301†), OSVDB (10569†), SecurityTracker (ID 1011484†) and Vulnerability Center (SBV-15183†). See VDB-22852 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.4
VulDB Temp Score: 8.4
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: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
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
09/30/2004 🔍09/30/2004 🔍
10/01/2004 🔍
12/31/2004 🔍
12/31/2004 🔍
02/20/2005 🔍
05/20/2007 🔍
04/14/2015 🔍
07/19/2019 🔍
Sources
Advisory: marc.infoResearcher: Ahmad Muammar (y3dips)
Status: Not defined
CVE: CVE-2004-1573 (🔍)
GCVE (CVE): GCVE-0-2004-1573
GCVE (VulDB): GCVE-100-22853
X-Force: 17571
SecurityFocus: 11301 - AJ-Fork Insecure Default Permissions Vulnerability
OSVDB: 10569 - CVE-2004-1573 - AJ-Fork - Privilege Escalation Issue
SecurityTracker: 1011484
Vulnerability Center: 15183 - AJ-Fork 167 Documentation Recommend Insecure Permissions for Users.db.php, Medium
See also: 🔍
Entry
Created: 04/14/2015 13:31Updated: 07/19/2019 15:39
Changes: 04/14/2015 13:31 (60), 07/19/2019 15:39 (4)
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.