| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in SugarCRM 4.5.1/5.0.0. This vulnerability affects unknown code. The manipulation leads to path traversal. This vulnerability is documented as CVE-2008-2045. Additionally, an exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in SugarCRM 4.5.1/5.0.0. This issue affects an unknown code. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is:
Absolute path traversal vulnerability in SugarCRM Sugar Community Edition 4.5.1 and 5.0.0 allows remote attackers to read arbitrary files via a full path in the URL parameter to modules/Feeds/Feed.php, which places the contents into a related cache file in the .cache/feeds directory.
The weakness was released 05/01/2008 by Roberto Suggi Liverani (Website). The advisory is shared at sugarcrm.com. The identification of this vulnerability is CVE-2008-2045 since 05/01/2008. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
The exploit is available at exploit-db.com. It is declared as highly functional.
The vulnerability is also documented in the databases at X-Force (42087), Exploit-DB (5521), SecurityFocus (BID 28981†) and Secunia (SA30002†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
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
03/24/2008 🔍04/29/2008 🔍
05/01/2008 🔍
05/01/2008 🔍
05/01/2008 🔍
03/16/2015 🔍
10/21/2024 🔍
Sources
Advisory: sugarcrm.comResearcher: Roberto Suggi Liverani
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-2045 (🔍)
GCVE (CVE): GCVE-0-2008-2045
GCVE (VulDB): GCVE-100-42221
X-Force: 42087 - Sugar Community Edition Feed.php information disclosure
SecurityFocus: 28981 - SugarCRM Community Edition RSS Module Information Disclosure Vulnerability
Secunia: 30002 - Sugar Community Edition RSS Module Information Disclosure Vulnerability, Less Critical
Vupen: ADV-2008-1388
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/16/2015 17:00Updated: 10/21/2024 08:17
Changes: 03/16/2015 17:00 (52), 09/23/2018 08:53 (10), 10/21/2024 08:17 (17)
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.