| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Tribiq CMS 5.0.9a. It has been rated as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to improper authentication. This vulnerability is referenced as CVE-2008-6804. Furthermore, an exploit is available. It is still unclear if this vulnerability genuinely exists.
Details
A vulnerability, which was classified as critical, has been found in Tribiq CMS 5.0.9a (Content Management System). This issue affects an unknown function. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
** DISPUTED ** Tribiq CMS 5.0.9a beta allows remote attackers to bypass authentication and gain administrative access by setting the COOKIE_LAST_ADMIN_USER and COOKIE_LAST_ADMIN_LANG cookies. NOTE: a third party reports that the vendor disputes the existence of this issue.
The weakness was published 05/11/2009 (Website). The advisory is shared at milw0rm.com. The identification of this vulnerability is CVE-2008-6804 since 05/11/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 unknown but a public exploit is available.
A public exploit has been developed by ZoRLu and been published even before and not after the advisory. The exploit is available at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 192 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment.
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 (46237), Exploit-DB (6886) and SecurityFocus (BID 32001†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: ZoRLu
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
10/31/2008 🔍10/31/2008 🔍
10/31/2008 🔍
05/11/2009 🔍
05/11/2009 🔍
05/11/2009 🔍
03/17/2015 🔍
11/09/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Confirmed
Disputed: 🔍
CVE: CVE-2008-6804 (🔍)
GCVE (CVE): GCVE-0-2008-6804
GCVE (VulDB): GCVE-100-48125
X-Force: 46237 - Tribiq CMS cookie authentication bypass
SecurityFocus: 32001 - RETIRED: Tribiq CMS Cookie Authentication Bypass Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 23:38Updated: 11/09/2024 15:21
Changes: 03/17/2015 23:38 (55), 11/07/2018 16:50 (7), 11/09/2024 15:21 (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.