dbcve.org
SametimeApplication · Ibm

CVE-2013-3975

MEDIUM · 5.0 CVSS v2.0 Published 2014-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in the Meeting Server in IBM Sametime 8.x through 8.5.2.1 and 9.x through 9.0.0.1 allows remote attackers to discover user names, full names, and e-mail addresses via a search.

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 confidence

The Meeting Server component in IBM Sametime 8.x through 8.5.2.1 and 9.x through 9.0.0.1 contains an unspecified vulnerability that allows remote attackers to discover user names, full names, and e-mail addresses via the search functionality without proper authorization controls.

MitigationApply vendor patches or upgrade to a Sametime version beyond 9.0.0.1 that addresses this issue. If patching is not immediately feasible, restrict network access to the Meeting Server and review search access controls.

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
SametimeApplication
Affected:= 8.0.0.0= 8.0.1.0= 8.0.1.1= 8.0.2.0= 8.0.2.1= 8.5.0.0= 8.5.1.0= 8.5.1.1= 8.5.2.0= 8.5.2.1= 9.0.0.0= 9.0.0.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM Sametime version
    Locate the Sametime installation and determine the exact version number
    Affected if The installed version matches 8.0.0.0 through 8.5.2.1 or 9.0.0.0 through 9.0.0.1
  2. Confirm Meeting Server component is present
    Determine if the Meeting Server component is installed and running within the Sametime environment
    Affected if Meeting Server is installed and enabled in the Sametime deployment
  3. Verify search functionality is accessible
    Determine if the Meeting Server search feature is network-accessible without authentication
    Affected if The search endpoint can be reached by remote users without proper authorization controls

Your environment is affected if you are running any of the listed affected versions with the Meeting Server component enabled and its search feature accessible to unauthorized users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches or upgrade to a Sametime version beyond 9.0.0.1 that addresses this issue. If patching is not immediately feasible, restrict network access to the Meeting Server and review search access controls.

Fix this in Sametime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-3975 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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