GeekLog 1.3.5 comment.php pid sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in GeekLog 1.3.5. Affected by this issue is some unknown functionality of the file comment.php. The manipulation of the argument pid leads to sql injection. This vulnerability is traded as CVE-2002-0963. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in GeekLog 1.3.5 (Blog Software). It has been rated as critical. This issue affects some unknown processing of the file comment.php. The manipulation of the argument pid with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality. The summary by CVE is:

SQL injection vulnerability in comment.php for GeekLog 1.3.5 and earlier allows remote attackers to obtain sensitive user information via the pid parameter.

The bug was discovered 06/10/2002. The weakness was shared 10/04/2002 by Ahmet Sabri ALPER (Website). It is possible to read the advisory at archives.neohapsis.com. The identification of this vulnerability is CVE-2002-0963. 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 of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 116 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:comment.php it is possible to find vulnerable targets with Google Hacking. The commercial vulnerability scanner Qualys is able to test this issue with plugin 10716 (Geeklog pid CGI Variable SQL Injection Vulnerability).

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 (9311), SecurityFocus (BID 4968†), OSVDB (8031†) and Vulnerability Center (SBV-6377†). The entry VDB-18898 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/10/2002 🔍
06/10/2002 +0 days 🔍
10/04/2002 +116 days 🔍
10/04/2002 +0 days 🔍
10/04/2002 +0 days 🔍
12/09/2004 +797 days 🔍
07/29/2014 +3519 days 🔍
06/04/2019 +1771 days 🔍

Sourcesinfo

Advisory: archives.neohapsis.com
Researcher: Ahmet Sabri ALPER
Status: Not defined
Confirmation: 🔍

CVE: CVE-2002-0963 (🔍)
GCVE (CVE): GCVE-0-2002-0963
GCVE (VulDB): GCVE-100-18899
X-Force: 9311
SecurityFocus: 4968 - Geeklog pid CGI Variable SQL Injection Vulnerability
OSVDB: 8031 - Geeklog - pid CGI Variable SQL Injection Vulnerability
Vulnerability Center: 6377 - Geeklog 1.3.5 Allows Obtaining Information via SQL Injection, Medium

See also: 🔍

Entryinfo

Created: 07/29/2014 11:32
Updated: 06/04/2019 09:17
Changes: 07/29/2014 11:32 (62), 06/04/2019 09:17 (3)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!