First published: Fri Apr 03 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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2009-1239 has a medium severity rating due to its potential to expose sensitive information.
To fix CVE-2009-1239, upgrade IBM DB2 to version 9.1 FP7 or a later version.
If CVE-2009-1239 is not addressed, attackers may exploit it to obtain sensitive information through crafted queries.
CVE-2009-1239 affects all IBM DB2 9.1 versions before FP7.
You can verify your vulnerability to CVE-2009-1239 by checking your IBM DB2 version and ensuring it is updated to FP7 or later.