| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in DotClear. It has been classified as problematic. The affected element is an unknown function of the file /inc/session.php. The manipulation leads to information disclosure. There is not any exploit available.
Details
A vulnerability was found in DotClear (Blog Software) (unknown version). It has been rated as problematic. This issue affects an unknown code block of the file /inc/session.php. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.
The weakness was released 07/21/2006 by Silitix (Website). The advisory is shared at archives.neohapsis.com. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After even before and not, there has been an exploit disclosed. By approaching the search of inurl:inc/session.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 vulnerability database at OSVDB (29820†). Entries connected to this vulnerability are available at VDB-84755, VDB-84756, VDB-84757 and VDB-84758. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.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: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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
07/21/2006 🔍07/21/2006 🔍
09/21/2006 🔍
05/08/2016 🔍
11/23/2018 🔍
Sources
Advisory: archives.neohapsis.comResearcher: Silitix
Status: Not defined
GCVE (VulDB): GCVE-100-84761
OSVDB: 29820 - DotClear /inc/session.php Direct Request Path Disclosure
See also: 🔍
Entry
Created: 05/08/2016 20:05Updated: 11/23/2018 10:53
Changes: 05/08/2016 20:05 (39), 11/23/2018 10:53 (2)
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.