| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in rateit 2.2. Affected is an unknown function of the file rateit.php. This manipulation of the argument rateit_id causes sql injection. This vulnerability is tracked as CVE-2006-1798. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability has been found in rateit 2.2 and classified as critical. Affected by this vulnerability is an unknown code of the file rateit.php. The manipulation of the argument rateit_id with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in rateit.php in RateIt 2.2 allows remote attackers to execute arbitrary SQL commands via the rateit_id parameter.
The weakness was disclosed 04/14/2006 by Aliaksandr Hartsuyeu (Website). The advisory is shared at vupen.com. This vulnerability is known as CVE-2006-1798 since 04/17/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
It is declared as proof-of-concept. By approaching the search of inurl:rateit.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 (25801), SecurityFocus (BID 17518†), OSVDB (24622†), Secunia (SA19637†) and SecurityTracker (ID 1015983†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/14/2006 🔍04/14/2006 🔍
04/14/2006 🔍
04/14/2006 🔍
04/17/2006 🔍
04/18/2006 🔍
04/24/2006 🔍
03/12/2015 🔍
07/24/2018 🔍
Sources
Advisory: vupen.com⛔Researcher: Aliaksandr Hartsuyeu
Status: Not defined
CVE: CVE-2006-1798 (🔍)
GCVE (CVE): GCVE-0-2006-1798
GCVE (VulDB): GCVE-100-29677
X-Force: 25801 - RateIt rateit.php SQL injection
SecurityFocus: 17518 - RateIt Rateit.PHP SQL Injection Vulnerability
Secunia: 19637 - RateIt "rateit_id" SQL Injection Vulnerability, Moderately Critical
OSVDB: 24622 - RateIt rateit.php rateit_id Parameter SQL Injection
SecurityTracker: 1015983
Vupen: ADV-2006-1358
Entry
Created: 03/12/2015 12:19Updated: 07/24/2018 10:09
Changes: 03/12/2015 12:19 (58), 07/24/2018 10:09 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.