What is the severity of CVE-2010-1454?

CVE-2010-1454 is considered a high severity vulnerability due to its potential for allowing unauthorized remote access to JMX resources.

How do I fix CVE-2010-1454?

To fix CVE-2010-1454, upgrade VMware SpringSource tc Server to version 6.0.20.D or later, or 6.0.25.A-SR01 or later.

What software is affected by CVE-2010-1454?

CVE-2010-1454 affects VMware SpringSource tc Server versions 6.0.19, 6.0.20, and 6.0.25.A before 6.0.25.A-SR01.

What type of attack can exploit CVE-2010-1454?

CVE-2010-1454 can be exploited by remote attackers to obtain sensitive information from JMX interfaces without proper encryption.

Is user intervention required to exploit CVE-2010-1454?

No, CVE-2010-1454 can be exploited remotely without user interaction, making it particularly dangerous.

Vulnerability/
CVE-2010-1454

medium

6.8

CWE

287

19/5/2010

7/8/2024

CVE-2010-1454

First published: Wed May 19 2010(Updated: )

com.springsource.tcserver.serviceability.rmi.JmxSocketListener in VMware SpringSource tc Server Runtime 6.0.19 and 6.0.20 before 6.0.20.D, and 6.0.25.A before 6.0.25.A-SR01, does not properly enforce the requirement for an encrypted (aka s2enc) password, which allows remote attackers to obtain JMX interface access via a blank password.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Vmware Tc Server	=6.0.25.a
Vmware Tc Server	=6.0.20.a
Vmware Tc Server	=6.0.20.b
Vmware Tc Server	=6.0.19.a
Vmware Tc Server	=6.0.20
Vmware Tc Server	=6.0.20.c
Vmware Tc Server	=6.0.19

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2010-1454?
CVE-2010-1454 is considered a high severity vulnerability due to its potential for allowing unauthorized remote access to JMX resources.
How do I fix CVE-2010-1454?
To fix CVE-2010-1454, upgrade VMware SpringSource tc Server to version 6.0.20.D or later, or 6.0.25.A-SR01 or later.
What software is affected by CVE-2010-1454?
CVE-2010-1454 affects VMware SpringSource tc Server versions 6.0.19, 6.0.20, and 6.0.25.A before 6.0.25.A-SR01.
What type of attack can exploit CVE-2010-1454?
CVE-2010-1454 can be exploited by remote attackers to obtain sensitive information from JMX interfaces without proper encryption.
Is user intervention required to exploit CVE-2010-1454?
No, CVE-2010-1454 can be exploited remotely without user interaction, making it particularly dangerous.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/references
agent/weakness
agent/author
agent/description
agent/first-publish-date
agent/tags
agent/event
agent/source
vendor/vmware
canonical/vmware tc server
version/vmware tc server/6.0.25.a
version/vmware tc server/6.0.20.a
version/vmware tc server/6.0.20.b
version/vmware tc server/6.0.19.a
version/vmware tc server/6.0.20
version/vmware tc server/6.0.20.c
version/vmware tc server/6.0.19

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-1454?
CVE-2010-1454 is considered a high severity vulnerability due to its potential for allowing unauthorized remote access to JMX resources.
How do I fix CVE-2010-1454?
To fix CVE-2010-1454, upgrade VMware SpringSource tc Server to version 6.0.20.D or later, or 6.0.25.A-SR01 or later.
What software is affected by CVE-2010-1454?
CVE-2010-1454 affects VMware SpringSource tc Server versions 6.0.19, 6.0.20, and 6.0.25.A before 6.0.25.A-SR01.
What type of attack can exploit CVE-2010-1454?
CVE-2010-1454 can be exploited by remote attackers to obtain sensitive information from JMX interfaces without proper encryption.
Is user intervention required to exploit CVE-2010-1454?
No, CVE-2010-1454 can be exploited remotely without user interaction, making it particularly dangerous.