| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Jath Pala cookiecheck 1.0. This issue affects some unknown processing of the file cookiecheck.php. The manipulation leads to access control. This vulnerability is listed as CVE-2008-6599. There is no available exploit.
Details
A vulnerability, which was classified as problematic, has been found in Jath Pala cookiecheck 1.0. This issue affects an unknown code of the file cookiecheck.php. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality. The summary by CVE is:
cookiecheck.php in CookieCheck 1.0 stores tmp/cc_sessions under the web root with insufficient access control, which allows remote attackers to obtain session data via a direct request related to the "default session save path."
The weakness was presented 04/15/2008 as tp://co (Website). The advisory is shared at code.google.com. The identification of this vulnerability is CVE-2008-6599 since 04/03/2009. 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 known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
By approaching the search of inurl:cookiecheck.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 (49827) and OSVDB (48865†). See VDB-3516, VDB-47987, VDB-50835 and VDB-55125 for similar entries. 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.3VulDB Meta Temp Score: 4.7
VulDB Base Score: 5.3
VulDB Temp Score: 4.7
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
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
04/15/2008 🔍10/06/2008 🔍
04/03/2009 🔍
04/03/2009 🔍
03/17/2015 🔍
11/04/2018 🔍
Sources
Advisory: tp://coStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2008-6599 (🔍)
GCVE (CVE): GCVE-0-2008-6599
GCVE (VulDB): GCVE-100-47513
X-Force: 49827 - CookieCheck cookiecheck.php information disclosure
OSVDB: 48865 - CookieCheck Default Session Save Path Unspecified Issue
See also: 🔍
Entry
Created: 03/17/2015 23:38Updated: 11/04/2018 08:23
Changes: 03/17/2015 23:38 (52), 11/04/2018 08:23 (3)
Complete: 🔍
Cache ID: 216:9CB: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.