CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.0 | $0-$5k | 0.00 |
A vulnerability classified as critical has been found in IBM DB2 8.0/9.1/9.5 (Database Software). This affects the function drop
. The manipulation with an unknown input leads to a remote code execution vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
IBM DB2 8 before FP18, 9.1 before FP8, 9.5 before FP4, and 9.7 before FP2 does not perform the expected drops of certain table functions upon a loss of privileges by the functions definers, which has unspecified impact and remote attack vectors.
The weakness was presented 09/28/2009 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2009-3471. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 42044 (IBM DB2 9.1 < Fix Pack 8 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases.
Upgrading to version 9.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (42044), SecurityFocus (BID 36540†), OSVDB (58477†) and Vulnerability Center (SBV-23704†). See VDB-48411, VDB-50285 and VDB-50284 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: Remote Code ExecutionCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
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 |
Nessus ID: 42044
Nessus Name: IBM DB2 9.1 < Fix Pack 8 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 801001
OpenVAS Name: IBM DB2 Multiple Vulnerabilities - Oct09 (Linux)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: DB2 9.1
Timeline
09/28/2009 🔍09/28/2009 🔍
09/29/2009 🔍
09/29/2009 🔍
09/29/2009 🔍
09/29/2009 🔍
09/29/2009 🔍
10/06/2009 🔍
10/12/2009 🔍
03/18/2015 🔍
08/23/2021 🔍
Sources
Vendor: ibm.comAdvisory: securityfocus.com⛔
Status: Not defined
Confirmation: 🔍
CVE: CVE-2009-3471 (🔍)
GCVE (CVE): GCVE-0-2009-3471
GCVE (VulDB): GCVE-100-50283
SecurityFocus: 36540 - IBM DB2 Multiple Unspecified Security Vulnerabilities
OSVDB: 58477 - IBM DB2 Universal Database Table Drop Function Definer Unspecifed Issue
Vulnerability Center: 23704 - IBM DB2 8 Prior to FP18, 9.1 Prior to FP8 and 9.5 before FP4 Remote Unspecified Vulnerability, High
See also: 🔍
Entry
Created: 03/18/2015 03:15 PMUpdated: 08/23/2021 11:19 AM
Changes: 03/18/2015 03:15 PM (61), 02/15/2017 09:31 AM (9), 08/23/2021 11:12 AM (4), 08/23/2021 11:19 AM (1)
Complete: 🔍
Cache ID: 18:2D3:40
No comments yet. Languages: en.
Please log in to comment.