VDB-84773 · SA20579 · OSVDB 29860

IBM DB2 Universal Database denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.3$0-$5k0.00

Summaryinfo

A vulnerability has been found in IBM DB2 Universal Database and classified as problematic. The impacted element is an unknown function. The manipulation leads to denial of service. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in IBM DB2 Universal Database (Database Software) (the affected version unknown). This issue affects an unknown part. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.

The bug was discovered 03/15/2005. The weakness was presented 05/15/2006 (Website). The advisory is shared at www-1.ibm.com. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 426 days. During that time the estimated underground price was around $5k-$25k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at OSVDB (29860†) and Secunia (SA20579†). See VDB-2317, VDB-2315, VDB-2316 and VDB-2313 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.3

VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/15/2005 🔍
05/15/2006 +426 days 🔍
06/14/2006 +29 days 🔍
08/18/2006 +65 days 🔍
05/08/2016 +3550 days 🔍
11/25/2018 +931 days 🔍

Sourcesinfo

Vendor: ibm.com

Advisory: www-1.ibm.com
Status: Not defined

GCVE (VulDB): GCVE-100-84773
Secunia: 20579 - DB2 Universal Database Multiple Denial of Service Vulnerabilities, Less Critical
OSVDB: 29860 - IBM DB2 Universal Database Crafted IN Clause SQL Query DoS

See also: 🔍

Entryinfo

Created: 05/08/2016 20:05
Updated: 11/25/2018 10:00
Changes: 05/08/2016 20:05 (44), 11/25/2018 10:00 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!