# CVE-2013-3975: Information disclosure in n/a

> Remote attackers can discover user names, full names, and email addresses via a search in IBM Sametime Meeting Server.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rm73-v38v-6gp7

## What is CVE-2013-3975?

CVE-2013-3975 is a medium-severity vulnerability in n/a, published on 26 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2013-3975?

It affects 1 product.


Products: Ibm Sametime.

## How do I fix CVE-2013-3975?

No fix has been published for CVE-2013-3975 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-3975 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3975 exists.

Public exploit code:

- IBM Lotus Notes Sametime User Enumeration (metasploit)

## Other vulnerabilities in n/a

- [CVE-2016-2972](https://insights.sbomify.com/CVE-2016-2972/): Information disclosure in Sametime (high 7.8)
- [CVE-2013-3983](https://insights.sbomify.com/CVE-2013-3983/): Open redirect in n/a (high 7.5)
- [CVE-2013-6742](https://insights.sbomify.com/CVE-2013-6742/): Information disclosure in n/a (high 7.5)
- [CVE-2013-3988](https://insights.sbomify.com/CVE-2013-3988/): Other in n/a (medium 6.8)
- [CVE-2016-0355](https://insights.sbomify.com/CVE-2016-0355/): Cross-site request forgery in Sametime (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3975 and fix it if it is affected.

What it is: CVE-2013-3975 is a medium-severity vulnerability in n/a, published on 26 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3975 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-3975/ (Markdown: https://insights.sbomify.com/CVE-2013-3975/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3975
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3975
- OSV: https://osv.dev/vulnerability/CVE-2013-3975

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-3975/
Summaries are generated and may contain mistakes; the official description above is the record.