What is the vulnerability severity of CVE-2011-4650?

CVE-2011-4650 has a medium severity level due to its potential to cause excessive CPU utilization.

How do I mitigate CVE-2011-4650?

To mitigate CVE-2011-4650, it is recommended to upgrade to a fixed release, such as version 6.0(0)SL1(0.14) or later.

What software versions are affected by CVE-2011-4650?

CVE-2011-4650 impacts Cisco Prime Data Center Network Manager version 5.2(1).

What causes the issue in CVE-2011-4650?

The issue in CVE-2011-4650 is caused by excessive logging during a TCP flood, leading to oversized log files.

Is there a workaround for CVE-2011-4650?

A temporary workaround for CVE-2011-4650 is to manage log sizes by implementing log rotation or monitoring logging levels.

Vulnerability/
CVE-2011-4650

high

7.5

CWE

399

7/8/2017

7/8/2024

CVE-2011-4650

First published: Mon Aug 07 2017(Updated: )

Cisco Data Center Network Manager is affected by Excessive Logging During a TCP Flood on Java Ports. If the size of server.log becomes very big because of too much logging by the DCNM server, then the CPU utilization increases. Known Affected Releases: 5.2(1). Known Fixed Releases: 6.0(0)SL1(0.14) 5.2(2.73)S0. Product identification: CSCtt15295.

Credit: ykramarz@cisco.com

Affected Software	Affected Version	How to fix
Cisco Prime Data Center Network Manager (DCNM)	=5.2\(1\)

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the vulnerability severity of CVE-2011-4650?
CVE-2011-4650 has a medium severity level due to its potential to cause excessive CPU utilization.
How do I mitigate CVE-2011-4650?
To mitigate CVE-2011-4650, it is recommended to upgrade to a fixed release, such as version 6.0(0)SL1(0.14) or later.
What software versions are affected by CVE-2011-4650?
CVE-2011-4650 impacts Cisco Prime Data Center Network Manager version 5.2(1).
What causes the issue in CVE-2011-4650?
The issue in CVE-2011-4650 is caused by excessive logging during a TCP flood, leading to oversized log files.
Is there a workaround for CVE-2011-4650?
A temporary workaround for CVE-2011-4650 is to manage log sizes by implementing log rotation or monitoring logging levels.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/author
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/cisco
canonical/cisco prime data center network manager (dcnm)
version/cisco prime data center network manager (dcnm)/5.2\(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 vulnerability severity of CVE-2011-4650?
CVE-2011-4650 has a medium severity level due to its potential to cause excessive CPU utilization.
How do I mitigate CVE-2011-4650?
To mitigate CVE-2011-4650, it is recommended to upgrade to a fixed release, such as version 6.0(0)SL1(0.14) or later.
What software versions are affected by CVE-2011-4650?
CVE-2011-4650 impacts Cisco Prime Data Center Network Manager version 5.2(1).
What causes the issue in CVE-2011-4650?
The issue in CVE-2011-4650 is caused by excessive logging during a TCP flood, leading to oversized log files.
Is there a workaround for CVE-2011-4650?
A temporary workaround for CVE-2011-4650 is to manage log sizes by implementing log rotation or monitoring logging levels.