CVE-2010-3739 ibm db2 universal database: Improper Authentication
ibm db2 universal database: no CVSS score yet. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.
On this page
The audit facility in the Security component in IBM DB2 UDB 9.5 before FP6a uses instance-level audit settings to capture connection (aka CONNECT and AUTHENTICATION) events in certain circumstances in which database-level audit settings were intended, which might make it easier for remote attackers to connect without discovery.
- EPSS
- 1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 67th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-287 Improper Authentication
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Patch: http://www-01.ibm.com/support/docview.wss?uid=swg1JR34218
- Vendor advisory: http://www-01.ibm.com/support/docview.wss?uid=swg1JR34218
Ask an AI about this CVE
Show the prompt
Explain CVE-2010-3739 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2010-3739?via=ask-ai-copy and https://cve.bz/cve/CVE-2010-3739?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2010-3739 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| ibm:db2_universal_database | through 9.5 |
| ibm:db2_universal_database | 9.5 |
| ibm:db2_universal_database | 9.5:fp1 |
| ibm:db2_universal_database | 9.5:fp2 |
| ibm:db2_universal_database | 9.5:fp2a |
| ibm:db2_universal_database | 9.5:fp3 |
| ibm:db2_universal_database | 9.5:fp3a |
| ibm:db2_universal_database | 9.5:fp3b |
| ibm:db2_universal_database | 9.5:fp4 |
| ibm:db2_universal_database | 9.5:fp4a |
| ibm:db2_universal_database | 9.5:fp5 |
Attack patterns (CAPEC)
- CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
- CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
- CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
- CAPEC-114 Authentication Abuse Severity: Medium
- CAPEC-115 Authentication Bypass Severity: Medium
- CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
- CAPEC-194 Fake the Source of Data Severity: Medium
- CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
- CAPEC-633 Token Impersonation Severity: Medium
- CAPEC-650 Upload a Web Shell to a Web Server Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.