| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in CYASK 3. This affects an unknown part of the file collect.php. Such manipulation of the argument neturl leads to path traversal. This vulnerability is documented as CVE-2008-4151. Additionally, an exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in CYASK 3. Affected by this issue is an unknown function of the file collect.php. The manipulation of the argument neturl 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. CVE summarizes:
Directory traversal vulnerability in collect.php in CYASK 3.x allows remote attackers to read arbitrary files via a .. (dot dot) in the neturl parameter.
The weakness was released 09/24/2008 (Website). The advisory is shared for download at securityfocus.com. This vulnerability is handled as CVE-2008-4151 since 09/19/2008. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1006.
The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:collect.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 (45238), Exploit-DB (6487) and SecurityFocus (BID 31237†). Once again VulDB remains the best source for vulnerability data.
Product
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
Class: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
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/18/2008 🔍09/19/2008 🔍
09/24/2008 🔍
09/24/2008 🔍
03/17/2015 🔍
11/04/2024 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2008-4151 (🔍)
GCVE (CVE): GCVE-0-2008-4151
GCVE (VulDB): GCVE-100-44156
X-Force: 45238 - Cyask collect.php file include
SecurityFocus: 31237 - Cyask 'collect.php' Information Disclosure Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 16:11Updated: 11/04/2024 10:15
Changes: 03/17/2015 16:11 (53), 10/09/2018 10:48 (4), 11/04/2024 10:15 (22)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.