Battelle V2I Hub 2.5.1 Back-End Database PluginStatusActions.php jtSorting/id sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.7 | $0-$5k | 0.00 |
A vulnerability was found in Battelle V2I Hub 2.5.1. It has been declared as critical. This vulnerability affects an unknown function of the file /api/PluginStatusActions.php of the component Back-End Database. The manipulation of the argument jtSorting/id
as part of a Parameter 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. CVE summarizes:
Battelle V2I Hub 2.5.1 is vulnerable to SQL injection. A remote authenticated attacker could send specially-crafted SQL statements to /api/PluginStatusActions.php and /status/pluginStatus.php using the jtSorting or id parameter, which could allow the attacker to view, add, modify or delete information in the back-end database.
The bug was discovered 08/09/2018. The weakness was shared 12/28/2018 (Website). The advisory is shared for download at exchange.xforce.ibmcloud.com. This vulnerability was named CVE-2018-1000630 since 08/01/2018. The exploitation appears to be easy. The attack can be initiated remotely. The successful exploitation requires a single authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
The vulnerability was handled as a non-public zero-day exploit for at least 141 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:api/PluginStatusActions.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 entries 128465, 128463, 128462 and 128461 are related to this item.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
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: 🔍
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: 🔍
0-Day Time: 🔍
Timeline
08/01/2018 🔍08/09/2018 🔍
12/28/2018 🔍
12/28/2018 🔍
12/29/2018 🔍
06/22/2023 🔍
Sources
Advisory: exchange.xforce.ibmcloud.comStatus: Not defined
CVE: CVE-2018-1000630 (🔍)
X-Force: 147307
See also: 🔍
Entry
Created: 12/29/2018 11:20Updated: 06/22/2023 10:05
Changes: 12/29/2018 11:20 (60), 04/24/2020 16:40 (1), 06/22/2023 10:05 (3)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.