What is the severity of CVE-2009-3473?

CVE-2009-3473 has an unspecified severity rating but poses remote attack vectors.

How do I fix CVE-2009-3473?

To mitigate CVE-2009-3473, upgrade to IBM DB2 9.1 Fix Pack 8 or later.

What versions of IBM DB2 are affected by CVE-2009-3473?

IBM DB2 versions 9.1 before Fix Pack 8, including FP1 to FP7, are affected by CVE-2009-3473.

What is the impact of CVE-2009-3473?

The impact of CVE-2009-3473 lies in the lack of required privileges for session authorization, potentially allowing unauthorized actions.

Can CVE-2009-3473 be exploited remotely?

Yes, CVE-2009-3473 can be exploited through unspecified remote attack vectors.

Vulnerability/
CVE-2009-3473

critical

CWE

29/9/2009

7/8/2024

CVE-2009-3473

First published: Tue Sep 29 2009(Updated: )

IBM DB2 9.1 before FP8 does not require the SETSESSIONUSER privilege for the SET SESSION AUTHORIZATION statement, which has unspecified impact and remote attack vectors.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
IBM Db2	=9.1-fp4
IBM Db2	=9.1-fp1
IBM Db2	=9.1-fp5
IBM Db2	=9.1-fp3
IBM Db2	=9.1-fp6
IBM Db2	=9.1-fp2
IBM Db2	=9.1-fp7

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2009-3473?
CVE-2009-3473 has an unspecified severity rating but poses remote attack vectors.
How do I fix CVE-2009-3473?
To mitigate CVE-2009-3473, upgrade to IBM DB2 9.1 Fix Pack 8 or later.
What versions of IBM DB2 are affected by CVE-2009-3473?
IBM DB2 versions 9.1 before Fix Pack 8, including FP1 to FP7, are affected by CVE-2009-3473.
What is the impact of CVE-2009-3473?
The impact of CVE-2009-3473 lies in the lack of required privileges for session authorization, potentially allowing unauthorized actions.
Can CVE-2009-3473 be exploited remotely?
Yes, CVE-2009-3473 can be exploited through unspecified remote attack vectors.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/last-modified-date
agent/severity
agent/author
agent/weakness
agent/first-publish-date
agent/description
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/ibm
canonical/ibm db2
version/ibm db2/9.1-fp4
version/ibm db2/9.1-fp1
version/ibm db2/9.1-fp5
version/ibm db2/9.1-fp3
version/ibm db2/9.1-fp6
version/ibm db2/9.1-fp2
version/ibm db2/9.1-fp7

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2009-3473?
CVE-2009-3473 has an unspecified severity rating but poses remote attack vectors.
How do I fix CVE-2009-3473?
To mitigate CVE-2009-3473, upgrade to IBM DB2 9.1 Fix Pack 8 or later.
What versions of IBM DB2 are affected by CVE-2009-3473?
IBM DB2 versions 9.1 before Fix Pack 8, including FP1 to FP7, are affected by CVE-2009-3473.
What is the impact of CVE-2009-3473?
The impact of CVE-2009-3473 lies in the lack of required privileges for session authorization, potentially allowing unauthorized actions.
Can CVE-2009-3473 be exploited remotely?
Yes, CVE-2009-3473 can be exploited through unspecified remote attack vectors.