First published: Tue Sep 29 2009(Updated: )
IBM DB2 8 before FP18, 9.1 before FP8, and 9.5 before FP4 allows remote authenticated users to bypass intended access restrictions, and update, insert, or delete table rows, via unspecified vectors.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
IBM DB2 Universal Database | =8.0-fp11 | |
IBM DB2 Universal Database | =8.0-fp3 | |
IBM DB2 Universal Database | =8.0-fp10 | |
IBM DB2 Universal Database | =9.1-fp4 | |
IBM DB2 Universal Database | =9.1-fp1 | |
IBM DB2 Universal Database | =8.0-fp9 | |
IBM DB2 Universal Database | =8.0-fp4 | |
IBM DB2 Universal Database | =9.1-fp5 | |
IBM DB2 Universal Database | =9.5-fp1 | |
IBM DB2 Universal Database | =8.0-fp16 | |
IBM DB2 Universal Database | =9.1-fp3 | |
IBM DB2 Universal Database | =8.0-fp6 | |
IBM DB2 Universal Database | =8.0-fp8 | |
IBM DB2 Universal Database | =8.0-fp14 | |
IBM DB2 Universal Database | =9.1-fp6 | |
IBM DB2 Universal Database | =8.0-fp2 | |
IBM DB2 Universal Database | =8.0-fp1 | |
IBM DB2 Universal Database | =8.0-fp5 | |
IBM DB2 Universal Database | =8.0-fp17 | |
IBM DB2 Universal Database | =9.1-fp2 | |
IBM DB2 Universal Database | =8.0-fp13 | |
IBM DB2 Universal Database | =9.5-fp2 | |
IBM DB2 Universal Database | =9.1-fp7 | |
IBM DB2 Universal Database | =8.0-fp12 | |
IBM DB2 Universal Database | =9.5-fp3 | |
IBM DB2 Universal Database | =8.0-fp15 | |
IBM DB2 Universal Database | =8.0-fp7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2009-3472 is considered a medium severity vulnerability due to its ability to allow unauthorized access to sensitive data.
To fix CVE-2009-3472, it is essential to apply the latest fix pack for your version of IBM DB2.
CVE-2009-3472 affects remote authenticated users of IBM DB2 versions 8 and 9 prior to the specified fix packs.
If exploited, CVE-2009-3472 may allow attackers to bypass access restrictions, leading to data manipulation such as updates, inserts, or deletions.
While the best solution is to apply the fix, temporary mitigations may involve restricting remote authenticated user access until the fix is implemented.