CVE-2009-1239: Infoleak
Published Apr 3, 2009
·Updated
IBM DB2 9.1 before FP7 returns incorrect query results in certain situations related to the order of application of an INNER JOIN predicate and an OUTER JOIN predicate, which might allow attackers to obtain sensitive information via a crafted query.
Affected Software
17 affected components
IBM DB2<=9.1
IBM DB2=9.1
IBM DB2=9.1
IBM DB2=9.1
IBM DB2=9.1
IBM DB2=9.1
IBM DB2=9.1
IBM DB2=9.1-fp1
IBM DB2=9.1-fp1
IBM DB2=9.1-fp1
IBM DB2=9.1-fp2
IBM DB2=9.1-fp3
IBM DB2=9.1-fp3a
IBM DB2=9.1-fp4
IBM DB2=9.1-fp4a
IBM DB2=9.1-fp5
IBM DB2=9.1-fp6
Remediation
Patch Available
Patch Available
Event History
Apr 3, 2009
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Data Sourced
via NVD·06:30 PM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2009-1239?
CVE-2009-1239 has a medium severity rating due to its potential to expose sensitive information.
2
How do I fix CVE-2009-1239?
To fix CVE-2009-1239, upgrade IBM DB2 to version 9.1 FP7 or a later version.
3
What are the consequences of not addressing CVE-2009-1239?
If CVE-2009-1239 is not addressed, attackers may exploit it to obtain sensitive information through crafted queries.
4
Which versions of IBM DB2 are affected by CVE-2009-1239?
CVE-2009-1239 affects all IBM DB2 9.1 versions before FP7.
5
How can I verify if my IBM DB2 installation is vulnerable to CVE-2009-1239?
You can verify your vulnerability to CVE-2009-1239 by checking your IBM DB2 version and ensuring it is updated to FP7 or later.