What is the severity of CVE-2009-2750?

CVE-2009-2750 is classified as a medium severity vulnerability.

How do I fix CVE-2009-2750?

To fix CVE-2009-2750, apply the latest fix pack or security patch provided by IBM for WSRR 6.3.0.

What type of attack is possible with CVE-2009-2750?

CVE-2009-2750 allows remote authenticated users to gain unauthorized access to unspecified data.

Is there a workaround for CVE-2009-2750?

There are no documented workarounds for mitigating CVE-2009-2750, updating to the latest version is recommended.

Vulnerability/
CVE-2009-2750

medium

5.5

CWE

4/2/2010

7/8/2024

CVE-2009-2750

First published: Thu Feb 04 2010(Updated: )

IBM WebSphere Service Registry and Repository (WSRR) 6.3.0 before FP2 does not have the intended configuration properties, which allows remote authenticated users to obtain unspecified data access via a property query.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
IBM WebSphere Service Registry and Repository	=6.3.0.1
IBM WebSphere Service Registry and Repository	=6.3.0

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2009-2750?
CVE-2009-2750 is classified as a medium severity vulnerability.
How do I fix CVE-2009-2750?
To fix CVE-2009-2750, apply the latest fix pack or security patch provided by IBM for WSRR 6.3.0.
What versions are affected by CVE-2009-2750?
CVE-2009-2750 affects IBM WebSphere Service Registry and Repository versions 6.3.0 and 6.3.0.1.
What type of attack is possible with CVE-2009-2750?
CVE-2009-2750 allows remote authenticated users to gain unauthorized access to unspecified data.
Is there a workaround for CVE-2009-2750?
There are no documented workarounds for mitigating CVE-2009-2750, updating to the latest version is recommended.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/references
agent/author
agent/weakness
agent/severity
agent/remedy
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/ibm
canonical/ibm websphere service registry and repository
version/ibm websphere service registry and repository/6.3.0.1
version/ibm websphere service registry and repository/6.3.0

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-2750?
CVE-2009-2750 is classified as a medium severity vulnerability.
How do I fix CVE-2009-2750?
To fix CVE-2009-2750, apply the latest fix pack or security patch provided by IBM for WSRR 6.3.0.
What versions are affected by CVE-2009-2750?
CVE-2009-2750 affects IBM WebSphere Service Registry and Repository versions 6.3.0 and 6.3.0.1.
What type of attack is possible with CVE-2009-2750?
CVE-2009-2750 allows remote authenticated users to gain unauthorized access to unspecified data.
Is there a workaround for CVE-2009-2750?
There are no documented workarounds for mitigating CVE-2009-2750, updating to the latest version is recommended.

CVE-2009-2750

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2009-2750?

How do I fix CVE-2009-2750?

What versions are affected by CVE-2009-2750?

What type of attack is possible with CVE-2009-2750?

Is there a workaround for CVE-2009-2750?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2009-2750?

How do I fix CVE-2009-2750?

What versions are affected by CVE-2009-2750?

What type of attack is possible with CVE-2009-2750?

Is there a workaround for CVE-2009-2750?