Tc ServerApplication · VMware
CVE-2010-1454
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedcom.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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe JmxSocketListener class in VMware SpringSource tc Server fails to enforce the requirement for an encrypted (s2enc) password, allowing remote attackers to access the JMX management interface using a blank password.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Tc ServerApplication
= 6.0.19= 6.0.19.a= 6.0.20= 6.0.20.a= 6.0.20.b= 6.0.20.c= 6.0.25.aCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify VMware Tc Server versionCheck the version.properties or VERSION file in the tc Server installation directory, or run: catalina.sh version (or catalina.bat version on Windows)Affected if Version matches 6.0.19, 6.0.19.a, 6.0.20, 6.0.20.a, 6.0.20.b, 6.0.20.c, or 6.0.25.a
-
Verify JMX is configuredCheck server.xml or context.xml for JmxSocketListener or any JMX-related listener configuration. Also check conf/server.xml for <Listener className="org.apache.catalina.mbeans.JmxRemoteLifecycleListener".../>Affected if JmxSocketListener or JMX listener is configured and enabled in the tc Server configuration
-
Check JMX network accessibilityReview server.xml for the JMX connector port binding (default 6969) and verify if it listens on 0.0.0.0 or an external interface rather than localhost only. Check firewall rules for inbound access to JMX ports.Affected if JMX listener binds to a reachable network interface (not localhost) and is exposed to the network
-
Inspect JMX password configurationExamine the user credentials file (typically conf/tomcat-users.xml or a separate JMX password file referenced in the configuration) for username/password entries. Check if passwords are stored in plain text or if an s2enc encrypted password is used.Affected if Password is blank, stored in plain text, or the s2enc encryption is not enforced/configured in the JMX authentication setup
User is affected if running an affected tc Server version with JMX enabled, network-accessible, and using blank or unencrypted passwords instead of s2enc-protected credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches (6.0.20.D or 6.0.25.A-SR01) and ensure JMX passwords are properly encrypted; restrict network access to JMX ports.
Fix this in Tc Server
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-1454 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data