| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Explay CMS 2.0/2.1. It has been classified as problematic. This vulnerability affects unknown code. This manipulation causes improper authentication. This vulnerability is tracked as CVE-2008-6411. Moreover, an exploit is present.
Details
A vulnerability classified as critical was found in Explay CMS 2.0/2.1 (Content Management System). Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Explay CMS 2.1 and earlier allows remote attackers to bypass authentication and gain administrative access by setting the login cookie to 1.
The weakness was disclosed 03/06/2009 (Website). The advisory is shared at milw0rm.com. This vulnerability is known as CVE-2008-6411 since 03/05/2009. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available.
A public exploit has been developed by Stack and been published even before and not after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 167 days. During that time the estimated underground price was around $0-$5k.
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 (45300), Exploit-DB (6500) and SecurityFocus (BID 31270†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Author: Stack
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
09/20/2008 🔍09/20/2008 🔍
09/20/2008 🔍
03/05/2009 🔍
03/06/2009 🔍
03/06/2009 🔍
03/17/2015 🔍
11/04/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Confirmed
CVE: CVE-2008-6411 (🔍)
GCVE (CVE): GCVE-0-2008-6411
GCVE (VulDB): GCVE-100-47017
X-Force: 45300 - Explay CMS cookie authentication bypass
SecurityFocus: 31270 - Explay CMS Cookie Authentication Bypass Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 16:11Updated: 11/04/2024 10:34
Changes: 03/17/2015 16:11 (48), 10/31/2018 06:36 (13), 11/04/2024 10:34 (17)
Complete: 🔍
Cache ID: 216::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.