OpenTSDB 2.3.0 /q key/style/yrange/y2range command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenTSDB 2.3.0 and classified as critical. The affected element is an unknown function of the file /q. Executing a manipulation of the argument key/style/yrange/y2range as part of Parameter can lead to command injection. This vulnerability is tracked as CVE-2018-12972. The attack can be launched remotely. No exploit exists.
Details
A vulnerability has been found in OpenTSDB 2.3.0 and classified as critical. This vulnerability affects an unknown code of the file /q. The manipulation of the argument key/style/yrange/y2range as part of a Parameter leads to a command injection vulnerability. The CWE definition for the vulnerability is CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered in OpenTSDB 2.3.0. Many parameters to the /q URI can execute commands, including o, key, style, and yrange and y2range and their JSON input.
The bug was discovered 06/29/2018. The weakness was disclosed 06/29/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2018-12972 since 06/28/2018. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1202 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry VDB-120083 is pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: 🔍
Timeline
06/28/2018 🔍06/29/2018 🔍
06/29/2018 🔍
06/29/2018 🔍
06/29/2018 🔍
03/29/2023 🔍
Sources
Product: github.comAdvisory: 1239
Status: Not defined
CVE: CVE-2018-12972 (🔍)
GCVE (CVE): GCVE-0-2018-12972
GCVE (VulDB): GCVE-100-120082
See also: 🔍
Entry
Created: 06/29/2018 17:47Updated: 03/29/2023 12:50
Changes: 06/29/2018 17:47 (57), 02/23/2020 09:48 (1), 03/29/2023 12:50 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.