DotClear 1.2.1/1.2.2/1.2.3/1.2.4 Error Message edit_cat.php information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in DotClear 1.2.1/1.2.2/1.2.3/1.2.4. It has been rated as problematic. The impacted element is an unknown function of the file edit_cat.php of the component Error Message Handler. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2006-3938. Moreover, an exploit is present.
Details
A vulnerability was found in DotClear 1.2.1/1.2.2/1.2.3/1.2.4 (Blog Software) and classified as problematic. This issue affects an unknown function of the file edit_cat.php of the component Error Message Handler. 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 summary by CVE is:
DotClear allows remote attackers to obtain sensitive information via a direct request for (1) edit_cat.php, (2) index.php, (3) edit_link.php in ecrire/tools/blogroll/; (4) syslog/index.php, (5) thememng/index.php, (6) toolsmng/index.php, (7) utf8convert/index.php in /ecrire/tools/; (8) /ecrire/inc/connexion.php and (9) /inc/session.php; (10) class.blog.php, (11) class.blogcomment.php, (12) and class.blogpost.php in /inc/classes/; (13) append.php, (14) class.xblog.php, (15) class.xblogcomment.php, and (16) class.xblogpost.php in /layout/; (17) form.php, (18) list.php, (19) post.php, or (20) template.php in /themes/default/, which reveal the installation path in error messages.
The weakness was disclosed 07/21/2006 by Silitix as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2006-3938 since 07/31/2006. 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 as well as a exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After even before and not, there has been an exploit disclosed. It is declared as highly functional. By approaching the search of inurl:edit_cat.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 (27913) and OSVDB (29812†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
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
07/21/2006 🔍07/21/2006 🔍
07/31/2006 🔍
07/31/2006 🔍
09/21/2006 🔍
03/12/2015 🔍
08/01/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Silitix
Status: Not defined
CVE: CVE-2006-3938 (🔍)
GCVE (CVE): GCVE-0-2006-3938
GCVE (VulDB): GCVE-100-31577
X-Force: 27913 - DotClear multiple .php scripts path disclosure
OSVDB: 29812 - DotClear /ecrire/tools/blogroll/edit_cat.php Direct Request Path Disclosure
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 14:25Updated: 08/01/2018 09:30
Changes: 03/12/2015 14:25 (50), 08/01/2018 09:30 (7)
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.