| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in IBM QRadar SIEM up to 7.2.6. Affected is an unknown function. The manipulation results in sql injection. This vulnerability is identified as CVE-2016-2873. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical has been found in IBM QRadar SIEM up to 7.2.6 (Log Management Software). Affected is an unknown functionality. The manipulation 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. CVE summarizes:
SQL injection vulnerability in IBM QRadar SIEM 7.1 before MR2 Patch 13 and 7.2 before 7.2.7 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.
The bug was discovered 07/26/2016. The weakness was released 11/30/2016 (Website). The advisory is available at www-01.ibm.com. This vulnerability is traded as CVE-2016-2873 since 03/09/2016. The exploitability is told to be easy. It is possible to launch the attack remotely. The successful exploitation needs a authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 127 days. During that time the estimated underground price was around $5k-$25k.
Upgrading to version 7.2.7 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 95000†). Entries connected to this vulnerability are available at VDB-93910, VDB-93909, VDB-93908 and VDB-93907. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.6
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Sql injectionCWE: CWE-89 / 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: QRadar SIEM 7.2.7
Timeline
03/09/2016 🔍07/26/2016 🔍
11/30/2016 🔍
11/30/2016 🔍
12/01/2016 🔍
12/21/2016 🔍
06/13/2019 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-2873 (🔍)
GCVE (CVE): GCVE-0-2016-2873
GCVE (VulDB): GCVE-100-93906
SecurityFocus: 95000 - IBM QRadar Security Information and Event Manager CVE-2016-2873 SQL Injection Vulnerability
See also: 🔍
Entry
Created: 12/01/2016 11:47Updated: 06/13/2019 12:42
Changes: 12/01/2016 11:47 (53), 06/13/2019 12:42 (13)
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.