What is the severity of CVE-2009-1231?

The severity of CVE-2009-1231 is currently unspecified due to the lack of details about the impact and attack vectors.

How do I fix CVE-2009-1231?

To address CVE-2009-1231, it is recommended to update IBM DB2 Content Manager to version 8.4.1.1 or later.

What versions of IBM DB2 Content Manager are affected by CVE-2009-1231?

CVE-2009-1231 affects IBM DB2 Content Manager version 8.4.1 prior to 8.4.1.1.

Can CVE-2009-1231 be exploited remotely?

The details on attack vectors for CVE-2009-1231 are unknown, so it is unclear if it can be exploited remotely.

Is there a workaround for CVE-2009-1231?

Currently, there are no documented workarounds for CVE-2009-1231 other than applying the patch to mitigate the vulnerability.

Vulnerability/
CVE-2009-1231

critical

CWE

2/4/2009

7/8/2024

CVE-2009-1231

First published: Thu Apr 02 2009(Updated: )

Unspecified vulnerability in the eClient in IBM DB2 Content Manager 8.4.1 before 8.4.1.1 has unknown impact and attack vectors.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
IBM DB2 Content Manager	=8.4.1

Remedy

http://www-01.ibm.com/support/docview.wss?uid=swg27015162

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2009-1231?
The severity of CVE-2009-1231 is currently unspecified due to the lack of details about the impact and attack vectors.
How do I fix CVE-2009-1231?
To address CVE-2009-1231, it is recommended to update IBM DB2 Content Manager to version 8.4.1.1 or later.
What versions of IBM DB2 Content Manager are affected by CVE-2009-1231?
CVE-2009-1231 affects IBM DB2 Content Manager version 8.4.1 prior to 8.4.1.1.
Can CVE-2009-1231 be exploited remotely?
The details on attack vectors for CVE-2009-1231 are unknown, so it is unclear if it can be exploited remotely.
Is there a workaround for CVE-2009-1231?
Currently, there are no documented workarounds for CVE-2009-1231 other than applying the patch to mitigate the vulnerability.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/last-modified-date
agent/weakness
agent/author
agent/remedy
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/ibm
canonical/ibm db2 content manager
version/ibm db2 content manager/8.4.1

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-1231?
The severity of CVE-2009-1231 is currently unspecified due to the lack of details about the impact and attack vectors.
How do I fix CVE-2009-1231?
To address CVE-2009-1231, it is recommended to update IBM DB2 Content Manager to version 8.4.1.1 or later.
What versions of IBM DB2 Content Manager are affected by CVE-2009-1231?
CVE-2009-1231 affects IBM DB2 Content Manager version 8.4.1 prior to 8.4.1.1.
Can CVE-2009-1231 be exploited remotely?
The details on attack vectors for CVE-2009-1231 are unknown, so it is unclear if it can be exploited remotely.
Is there a workaround for CVE-2009-1231?
Currently, there are no documented workarounds for CVE-2009-1231 other than applying the patch to mitigate the vulnerability.