Geeklog 1.3.11 Sr2/1.4.0 Beta1 Error Message search.php information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Geeklog 1.3.11 Sr2/1.4.0 Beta1. It has been classified as problematic. This vulnerability affects unknown code of the file search.php of the component Error Message Handler. The manipulation leads to information disclosure. This vulnerability is referenced as CVE-2005-4026. Furthermore, an exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Geeklog 1.3.11 Sr2/1.4.0 Beta1 (Blog Software). It has been rated as problematic. This issue affects an unknown code block of the file search.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:
search.php in Geeklog 1.4.x before 1.4.0rc1, and 1.3.x before 1.3.11sr3, allows remote attackers to obtain sensitive information via invalid (1) datestart and (2) dateend parameters, which leaks the web server path in an error message.
The weakness was published 11/28/2005 by r0t (Website). The advisory is shared at osvdb.org. The identification of this vulnerability is CVE-2005-4026 since 12/05/2005. 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 immediately, there has been an exploit disclosed. It is declared as proof-of-concept. By approaching the search of inurl:search.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.4.x eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (21398†). Similar entry is available at VDB-28038. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Proof-of-Concept
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Upgrade: Geeklog 1.4.x
Timeline
11/28/2005 🔍11/28/2005 🔍
12/02/2005 🔍
12/05/2005 🔍
12/05/2005 🔍
03/11/2015 🔍
07/14/2018 🔍
Sources
Advisory: osvdb.org⛔Researcher: r0t
Status: Not defined
Confirmation: 🔍
CVE: CVE-2005-4026 (🔍)
GCVE (CVE): GCVE-0-2005-4026
GCVE (VulDB): GCVE-100-27305
OSVDB: 21398 - Geeklog search.php Failed SQL Query Path Disclosure
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 07/14/2018 10:16
Changes: 03/11/2015 23:39 (50), 07/14/2018 10:16 (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.