| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in AlkalinePHP 0.80.00. It has been rated as critical. Affected by this issue is some unknown functionality of the file thread.php. Performing a manipulation of the argument ID results in sql injection. This vulnerability was named CVE-2008-2395. The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability, which was classified as critical, was found in AlkalinePHP 0.80.00. This affects an unknown function of the file thread.php. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in thread.php in AlkalinePHP 0.80.00 beta and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.
The weakness was presented 05/21/2008 by ERRor (Website). It is possible to read the advisory at milw0rm.com. This vulnerability is uniquely identified as CVE-2008-2395 since 05/21/2008. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
A public exploit has been developed in Perl. The exploit is shared for download at securityfocus.com. It is declared as highly functional. By approaching the search of inurl:thread.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 (42520), Exploit-DB (5652) and SecurityFocus (BID 29281†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Programming Language: 🔍
Download: 🔍
Google Hack: 🔍
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
05/19/2008 🔍05/21/2008 🔍
05/21/2008 🔍
05/21/2008 🔍
03/16/2015 🔍
10/24/2024 🔍
Sources
Advisory: milw0rm.com⛔Researcher: ERRor
Status: Not defined
CVE: CVE-2008-2395 (🔍)
GCVE (CVE): GCVE-0-2008-2395
GCVE (VulDB): GCVE-100-42483
X-Force: 42520 - AlkalinePHP thread.php SQL injection
SecurityFocus: 29281 - AlkalinePHP 'thread.php' SQL Injection Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/16/2015 17:00Updated: 10/24/2024 04:41
Changes: 03/16/2015 17:00 (48), 09/25/2018 12:48 (11), 10/24/2024 04:41 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.