| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Santostefano Giovanni ToyLog 0.1. This vulnerability affects unknown code of the file read.php. The manipulation of the argument idm leads to sql injection. This vulnerability is uniquely identified as CVE-2009-3750. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, has been found in Santostefano Giovanni ToyLog 0.1. This issue affects an unknown code of the file read.php. The manipulation of the argument idm 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, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in read.php in ToyLog 0.1 allows remote attackers to execute arbitrary SQL commands via the idm parameter.
The weakness was disclosed 07/10/2009 (Website). The advisory is shared at milw0rm.com. The identification of this vulnerability is CVE-2009-3750 since 10/22/2009. 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 public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
After immediately, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:read.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 (51633), Exploit-DB (9109), OSVDB (55804†) and Secunia (SA35791†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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: Proof-of-Concept
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: 🔍
Exploit Delay Time: 🔍
Timeline
07/10/2009 🔍07/10/2009 🔍
07/13/2009 🔍
07/13/2009 🔍
10/22/2009 🔍
10/22/2009 🔍
03/18/2015 🔍
12/03/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Not defined
CVE: CVE-2009-3750 (🔍)
GCVE (CVE): GCVE-0-2009-3750
GCVE (VulDB): GCVE-100-50537
X-Force: 51633
Secunia: 35791 - ToyLog "idm" SQL Injection Vulnerability, Moderately Critical
OSVDB: 55804 - ToyLog read.php idm Parameter SQL Injection
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/18/2015 15:15Updated: 12/03/2024 11:24
Changes: 03/18/2015 15:15 (57), 01/23/2019 08:08 (3), 12/03/2024 11:24 (21)
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.