| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ITROM Cart v1.0.x. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the file catalog.php. Performing a manipulation of the argument prodid results in sql injection. Remote exploitation of the attack is possible. Furthermore, an exploit is available. The suggested workaround should be applied.
Details
A vulnerability, which was classified as critical, was found in ITROM Cart v1.0.x. This affects an unknown function of the file catalog.php. The manipulation of the argument prodid 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 weakness was published 06/15/2011 as VL-ID 114 as not defined advisory (Website). The advisory is shared at vulnerability-lab.com. It is possible to initiate the attack remotely. Technical details and 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 shared for download at vulnerability-lab.com. It is declared as proof-of-concept. By approaching the search of inurl:catalog.php it is possible to find vulnerable targets with Google Hacking.
The best possible mitigation is suggested to be Workaround. The vulnerability will be addressed with the following lines of code:
$stmt = $dbh->prepare(INSERT INTO REGISTRY (name, value) VALUES (:name, :value)); $stmt->bindParam(name, $name); $stmt->bindParam(value, $value);
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.6
VulDB Base Score: 6.3
VulDB Temp Score: 5.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: 🔍
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: 🔍
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: WorkaroundStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
06/15/2011 🔍06/15/2011 🔍
09/06/2016 🔍
04/10/2019 🔍
Sources
Advisory: VL-ID 114Status: Not defined
GCVE (VulDB): GCVE-100-91245
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/06/2016 14:30Updated: 04/10/2019 16:43
Changes: 09/06/2016 14:30 (44), 04/10/2019 16:43 (1)
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.