| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in The Address Book and classified as critical. This issue affects some unknown processing of the file search.php. The manipulation leads to sql injection. This vulnerability is uniquely identified as CVE-2006-4575. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in The Address Book (the affected version unknown). It has been rated as critical. This issue affects an unknown part of the file search.php. The manipulation 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 weakness was disclosed 01/03/2007 with Secunia Research (Website). It is possible to read the advisory at secunia.com. The identification of this vulnerability is CVE-2006-4575 since 09/06/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 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.
By approaching the search of inurl:search.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 (31238), SecurityFocus (BID 21870†), OSVDB (32569†) and Secunia (SA21694†). The entries VDB-34121, VDB-34120, VDB-34119 and VDB-34118 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: 🔍
Status: Not defined
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: 🔍
Suricata ID: 2006003
Suricata Class: 🔍
Suricata Message: 🔍
Timeline
09/06/2006 🔍12/31/2006 🔍
01/03/2007 🔍
01/03/2007 🔍
01/03/2007 🔍
01/04/2007 🔍
05/08/2016 🔍
08/08/2022 🔍
Sources
Advisory: secunia.com⛔Organization: Secunia Research
Status: Not defined
CVE: CVE-2006-4575 (🔍)
GCVE (CVE): GCVE-0-2006-4575
GCVE (VulDB): GCVE-100-85067
X-Force: 31238
SecurityFocus: 21870 - The Address Book Multiple Remote Vulnerabilities
Secunia: 21694 - The Address Book Multiple Vulnerabilities, Highly Critical
OSVDB: 32569 - The Address Book search.php Multiple Parameter SQL Injection
See also: 🔍
Entry
Created: 05/08/2016 21:39Updated: 08/08/2022 20:44
Changes: 05/08/2016 21:39 (54), 12/16/2018 10:58 (6), 08/08/2022 20:44 (3)
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.