Ibm Db2 Universal Database Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

9.022
7.x14
8.x12
8.010
8.19

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix89
Temporary Fix0
Workaround2
Unavailable0
Not Defined15

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High1
Functional0
Proof-of-Concept50
Unproven2
Not Defined53

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined106
Physical0
Local0
Adjacent0
Network0

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined106
High0
Low0
None0

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined106
Required0
None0

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤30
≤42
≤55
≤626
≤719
≤86
≤94
≤1044

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤30
≤44
≤512
≤627
≤714
≤83
≤930
≤1016

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤30
≤42
≤55
≤626
≤719
≤86
≤94
≤1044

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k0
<2k1
<5k9
<10k23
<25k26
<50k44
<100k3
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k93
<2k3
<5k0
<10k2
<25k7
<50k1
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (23): 6.0, 6.1, 7, 7 FP12, 7.0, 7.1, 7.2 FP9, 8 FP12, 8 FP13, 8.0, 8.1, 8.1 FP6, 8.1 FP8, 8.2, 8.2 FP3, 8.2 FP16, 9.0, 9.1, 9.1 FP2, 9.2, 9.3, 9.4, XP

Link to Product Website: https://www.ibm.com/

Software Type: Database Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
10/05/20106.56.2IBM DB2 Universal Database Audit Facility improper authentication$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2010-3739
04/23/20106.35.7IBM DB2 Universal Database Data cryptographic issues$25k-$100k$0-$5kProof-of-ConceptOfficial Fix0.04CVE-2009-3555
12/02/20095.95.3IBM DB2 Universal Database User Account access control$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.03CVE-2009-4150
01/16/20095.34.8IBM DB2 Universal Database input validation$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.03CVE-2009-0173
01/16/20095.34.8IBM DB2 Universal Database input validation$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.03CVE-2009-0172
09/08/20089.89.4IBM DB2 Universal Database input validation$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2008-3960
08/28/20089.88.8IBM DB2 Universal Database information disclosure$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.05CVE-2008-3857
08/28/20089.89.4IBM DB2 Universal Database access control$25k-$100k$0-$5kNot DefinedOfficial Fix0.04CVE-2008-3856
08/28/20089.88.8IBM DB2 Universal Database Administration Server DAS access control$25k-$100k$0-$5kProof-of-ConceptOfficial Fix0.00CVE-2008-3855
08/28/20089.88.8IBM DB2 Universal Database sqlrlaka memory corruption$25k-$100k$0-$5kProof-of-ConceptOfficial Fix0.03CVE-2008-3854
08/28/200810.09.5IBM DB2 Universal Database DAS memory corruption$25k-$100k$0-$5kNot DefinedOfficial Fix0.05CVE-2008-3853
08/28/20089.88.8IBM DB2 Universal Database Stored Procedure access control$25k-$100k$0-$5kProof-of-ConceptOfficial Fix0.05CVE-2008-3852
06/09/20085.35.3IBM DB2 Universal Database Local Privilege Escalation$25k-$100k$0-$5kNot DefinedNot Defined0.05
04/16/20089.38.4IBM DB2 Universal Database Administration Server memory corruption$25k-$100k$0-$5kProof-of-ConceptOfficial Fix0.00CVE-2007-5758
04/16/20088.47.6IBM DB2 Universal Database Administration Server link following$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.00CVE-2007-5664
02/12/20085.35.3IBM DB2 Universal Database Local Privilege Escalation$25k-$100k$0-$5kNot DefinedNot Defined0.00
02/04/20089.89.4IBM DB2 Universal Database JAR File Administration resource management$25k-$100k$0-$5kNot DefinedOfficial Fix0.07CVE-2007-3676
02/04/20089.89.4IBM DB2 Universal Database SYSPROC.NNSTAT resource management$25k-$100k$0-$5kNot DefinedOfficial Fix0.09CVE-2007-3676
02/04/20089.88.5IBM DB2 Universal Database ATTACH resource management$5k-$25k$0-$5kUnprovenOfficial Fix0.02CVE-2007-3676
02/04/20089.98.9IBM DB2 Universal Database SetUID Binary memory corruption$25k-$100k$0-$5kProof-of-ConceptOfficial Fix0.05CVE-2008-0699
02/04/20089.88.8IBM DB2 Universal Database DB2DART memory corruption$25k-$100k$0-$5kProof-of-ConceptOfficial Fix0.03CVE-2008-0698
02/04/20089.18.2IBM DB2 Universal Database DB2 Commands access control$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.03CVE-2008-0697
02/04/20089.88.8IBM DB2 Universal Database SYSPROC.ADMIN_SP_C access control$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.03CVE-2008-0696
02/04/20089.88.5IBM DB2 Universal Database DAS access control$25k-$100k$0-$5kUnprovenOfficial Fix0.04CVE-2007-5757
02/04/20084.84.3IBM DB2 Universal Database DB2PD DB2INSTANCE access control$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.00CVE-2008-0696

81 more entries are not shown

more entries by Ibm

Might our Artificial Intelligence support you?

Check our Alexa App!