CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.9 | $0-$5k | 0.00 |
A vulnerability has been found in IBM DB2 9.5/9.7 (Database Software) and classified as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect integrity, and availability. The summary by CVE is:
IBM DB2 9.5 before FP7 and 9.7 before FP4 on Linux, UNIX, and Windows does not properly enforce privilege requirements for table access, which allows remote authenticated users to modify SYSSTAT.TABLES statistics columns via an UPDATE statement. NOTE: some of these details are obtained from third party information.
The weakness was disclosed 05/03/2011 (Website). It is possible to read the advisory at www-01.ibm.com. This vulnerability is known as CVE-2011-1847 since 05/03/2011. The attack can be launched remotely. The requirement for exploitation is a single authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 51841 (IBM DB2 9.5 < Fix Pack 7 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19656 (IBM DB2 Multiple Vulnerabilities (IC71413, IC72119)).
Upgrading to version 9.5 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (66979) and Tenable (51841). The entries 4278 and 57306 are pretty similar.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.4
VulDB Temp Score: 4.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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Nessus ID: 51841
Nessus Name: IBM DB2 9.5 < Fix Pack 7 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 801930
OpenVAS Name: IBM DB2 Multiple Security Bypass Vulnerabilities (May-11)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: DB2 9.5
Timeline
04/21/2011 🔍04/21/2011 🔍
04/21/2011 🔍
05/03/2011 🔍
05/03/2011 🔍
05/03/2011 🔍
05/22/2011 🔍
03/23/2015 🔍
11/05/2021 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2011-1847 (🔍)
OVAL: 🔍
X-Force: 66979
Vulnerability Center: 31497 - IBM DB2 9.5-9.5 FP6 and 9.7-9.7 FP3 Allows Remote SYSSTAT.TABLES Statistics Columns Modification, Medium
SecurityFocus: 47525 - IBM DB2 Multiple Security Bypass Vulnerabilities
Secunia: 44229 - IBM DB2 Two Vulnerabilities, Less Critical
Vupen: ADV-2011-1083
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 11/05/2021 15:06
Changes: 03/23/2015 16:50 (63), 03/22/2017 21:50 (14), 11/05/2021 15:06 (3)
Complete: 🔍
Cache ID: 18:8DD:103
No comments yet. Languages: en.
Please log in to comment.