CWE
264
Advisory Published
Updated

CVE-2009-3472

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 SoftwareAffected VersionHow 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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2009-3472?

    CVE-2009-3472 is considered a medium severity vulnerability due to its ability to allow unauthorized access to sensitive data.

  • How do I fix CVE-2009-3472?

    To fix CVE-2009-3472, it is essential to apply the latest fix pack for your version of IBM DB2.

  • Who is affected by CVE-2009-3472?

    CVE-2009-3472 affects remote authenticated users of IBM DB2 versions 8 and 9 prior to the specified fix packs.

  • What are the consequences of CVE-2009-3472?

    If exploited, CVE-2009-3472 may allow attackers to bypass access restrictions, leading to data manipulation such as updates, inserts, or deletions.

  • Is there a workaround for CVE-2009-3472?

    While the best solution is to apply the fix, temporary mitigations may involve restricting remote authenticated user access until the fix is implemented.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203