CVE-2011-1370
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 · uneditedThe default configuration of the Sametime configuration servlet (SCS) in the server in IBM Lotus Sametime 7.0 through 8.5.2 does not enable an authentication requirement, which allows remote attackers to read the configuration settings by examining a response message.
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 Sametime Configuration Servlet (SCS) in IBM Lotus Sametime versions 7.0 through 8.5.2 ships with a default configuration that does not require authentication, allowing unauthenticated remote attackers to retrieve sensitive configuration settings by examining server response messages.
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= 7.0= 7.5= 7.5.0.1= 7.5.1= 7.5.1.1= 7.5.1.2= 8.0= 8.0.1= 8.0.2= 8.5= 8.5.1= 8.5.2CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Confirm IBM Lotus Sametime installation and versionLocate the Sametime installation directory and check the version. In a standard installation, look for a version file or check the installation logs. Use the system console or package manager if available to verify the installed version falls within 7.0 through 8.5.2.Affected if The installed version is any of: 7.0, 7.5, 7.5.0.1, 7.5.1, 7.5.1.1, 7.5.1.2, 8.0, 8.0.1, 8.0.2, 8.5, 8.5.1, or 8.5.2.
-
Verify if Sametime Configuration Servlet (SCS) is exposedIdentify whether the Sametime Configuration Servlet is deployed and accessible on the server. The endpoint is typically accessed via HTTP/HTTPS on the Sametime server. Check the server's web application configuration to confirm SCS is enabled.Affected if The SCS is deployed and reachable over the network.
-
Test SCS endpoint without authentication credentialsSend an HTTP request to the SCS endpoint without providing any authentication headers or credentials. Observe the server response. A vulnerable server will return configuration data or status information without requiring authentication.Affected if The SCS responds with configuration data, server settings, or diagnostic information without any authentication challenge.
-
Inspect SCS authentication configurationExamine the Sametime server configuration files related to SCS. Look for settings that control authentication requirements on the configuration servlet. Check whether authentication is explicitly required or if the default (vulnerable) configuration is in place.Affected if The configuration shows authentication is not required for SCS, or the default configuration that shipped with the product is in use.
A user is affected if they run any IBM Lotus Sametime version 7.0-8.5.2 with the Sametime Configuration Servlet exposed and accessible without authentication, returning sensitive configuration data.
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 dataEnable authentication requirement on the Sametime Configuration Servlet (SCS) in the server configuration to prevent unauthenticated access to configuration data.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1370 — 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-2011-1370 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