What is the severity of CVE-2011-2330?

CVE-2011-2330 is considered to have a medium severity due to the risk posed by unauthorized access to restricted pages via the built-in account.

How do I fix CVE-2011-2330?

To fix CVE-2011-2330, it is recommended to update IBM Tivoli Management Framework to a version that addresses this vulnerability.

Which versions of IBM Tivoli Management Framework are affected by CVE-2011-2330?

CVE-2011-2330 affects IBM Tivoli Management Framework versions 3.7.1, 4.1, 4.1.1, and 4.3.1.

What is the impact of exploiting CVE-2011-2330?

Exploiting CVE-2011-2330 allows remote attackers to gain access to restricted resources through an uncontrolled built-in account.

Is there a workaround for CVE-2011-2330?

Currently, the best practice is to restrict access to TCP port 9495 and implement additional authentication measures.

Vulnerability/
CVE-2011-2330

critical

CWE

264

2/6/2011

6/8/2024

CVE-2011-2330

First published: Thu Jun 02 2011(Updated: )

Tivoli Endpoint in IBM Tivoli Management Framework 3.7.1, 4.1, 4.1.1, and 4.3.1 has an unspecified "built-in account" that is "trivially" accessed, which makes it easier for remote attackers to send requests to restricted pages via a session on TCP port 9495, a different vulnerability than CVE-2011-1220.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
IBM Tivoli Management Framework	=4.3.1
IBM Tivoli Management Framework	=3.7.1
IBM Tivoli Management Framework	=4.1
IBM Tivoli Management Framework	=4.1.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2011-2330?
CVE-2011-2330 is considered to have a medium severity due to the risk posed by unauthorized access to restricted pages via the built-in account.
How do I fix CVE-2011-2330?
To fix CVE-2011-2330, it is recommended to update IBM Tivoli Management Framework to a version that addresses this vulnerability.
Which versions of IBM Tivoli Management Framework are affected by CVE-2011-2330?
CVE-2011-2330 affects IBM Tivoli Management Framework versions 3.7.1, 4.1, 4.1.1, and 4.3.1.
What is the impact of exploiting CVE-2011-2330?
Exploiting CVE-2011-2330 allows remote attackers to gain access to restricted resources through an uncontrolled built-in account.
Is there a workaround for CVE-2011-2330?
Currently, the best practice is to restrict access to TCP port 9495 and implement additional authentication measures.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/last-modified-date
agent/severity
agent/weakness
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/ibm
canonical/ibm tivoli management framework
version/ibm tivoli management framework/4.3.1
version/ibm tivoli management framework/3.7.1
version/ibm tivoli management framework/4.1
version/ibm tivoli management framework/4.1.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-2011-2330?
CVE-2011-2330 is considered to have a medium severity due to the risk posed by unauthorized access to restricted pages via the built-in account.
How do I fix CVE-2011-2330?
To fix CVE-2011-2330, it is recommended to update IBM Tivoli Management Framework to a version that addresses this vulnerability.
Which versions of IBM Tivoli Management Framework are affected by CVE-2011-2330?
CVE-2011-2330 affects IBM Tivoli Management Framework versions 3.7.1, 4.1, 4.1.1, and 4.3.1.
What is the impact of exploiting CVE-2011-2330?
Exploiting CVE-2011-2330 allows remote attackers to gain access to restricted resources through an uncontrolled built-in account.
Is there a workaround for CVE-2011-2330?
Currently, the best practice is to restrict access to TCP port 9495 and implement additional authentication measures.