What is the severity of CVE-2010-4592?

CVE-2010-4592 has a severity rating that indicates it can cause a denial of service to affected systems.

How do I fix CVE-2010-4592?

To fix CVE-2010-4592, update IBM Lotus Mobile Connect to version 6.1.4 or later.

Which versions of IBM Lotus Mobile Connect are affected by CVE-2010-4592?

CVE-2010-4592 affects IBM Lotus Mobile Connect versions prior to 6.1.4, including 6.1.1, 6.1.2, and 6.1.3.

What types of attacks does CVE-2010-4592 allow?

CVE-2010-4592 allows remote attackers to cause a denial of service by exploiting the Mobile Network Connections functionality.

Is there a workaround for CVE-2010-4592 if I cannot update?

The recommended action is to update to a patched version, as no specific workaround has been documented for CVE-2010-4592.

Vulnerability/
CVE-2010-4592

medium

4.3

CWE

399

22/12/2010

11/1/2011

CVE-2010-4592

First published: Wed Dec 22 2010(Updated: )

The Mobile Network Connections functionality in the Connection Manager in IBM Lotus Mobile Connect before 6.1.4, when HTTP Access Services (HTTP-AS) is enabled, does not properly handle failed attempts at establishing HTTP-TCP sessions, which allows remote attackers to cause a denial of service (memory consumption and daemon crash) by making many TCP connection attempts.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
IBM Lotus Mobile Connect	=6.1.1.1
IBM Lotus Mobile Connect	=6.1.1
IBM Lotus Mobile Connect	<=6.1.3
IBM Lotus Mobile Connect	=6.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2010-4592?
CVE-2010-4592 has a severity rating that indicates it can cause a denial of service to affected systems.
How do I fix CVE-2010-4592?
To fix CVE-2010-4592, update IBM Lotus Mobile Connect to version 6.1.4 or later.
Which versions of IBM Lotus Mobile Connect are affected by CVE-2010-4592?
CVE-2010-4592 affects IBM Lotus Mobile Connect versions prior to 6.1.4, including 6.1.1, 6.1.2, and 6.1.3.
What types of attacks does CVE-2010-4592 allow?
CVE-2010-4592 allows remote attackers to cause a denial of service by exploiting the Mobile Network Connections functionality.
Is there a workaround for CVE-2010-4592 if I cannot update?
The recommended action is to update to a patched version, as no specific workaround has been documented for CVE-2010-4592.

agent/severity
agent/description
agent/type
agent/event
agent/softwarecombine
agent/first-publish-date
agent/last-modified-date
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
agent/weakness
agent/references
agent/author
vendor/ibm
canonical/ibm lotus mobile connect
version/ibm lotus mobile connect/6.1.1.1
version/ibm lotus mobile connect/6.1.1
version/ibm lotus mobile connect/6.1.3
version/ibm lotus mobile connect/6.1.2

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-2010-4592?
CVE-2010-4592 has a severity rating that indicates it can cause a denial of service to affected systems.
How do I fix CVE-2010-4592?
To fix CVE-2010-4592, update IBM Lotus Mobile Connect to version 6.1.4 or later.
Which versions of IBM Lotus Mobile Connect are affected by CVE-2010-4592?
CVE-2010-4592 affects IBM Lotus Mobile Connect versions prior to 6.1.4, including 6.1.1, 6.1.2, and 6.1.3.
What types of attacks does CVE-2010-4592 allow?
CVE-2010-4592 allows remote attackers to cause a denial of service by exploiting the Mobile Network Connections functionality.
Is there a workaround for CVE-2010-4592 if I cannot update?
The recommended action is to update to a patched version, as no specific workaround has been documented for CVE-2010-4592.