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

> Remote attackers can read session variables due to weak cookie domain settings in IBM Lotus Sametime Enterprise Meeting Server.

- **Severity:** Low 2.9 (`AV:A/AC:M/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:** 9 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qmc3-45w6-449f

## What is CVE-2013-3985?

CVE-2013-3985 is a low-severity vulnerability in n/a, published on 9 Nov 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Enterprise Meeting Server in IBM Lotus Sametime 8.5.2 and 8.5.2.1 does not properly restrict application cookies, which allows remote attackers to read session variables by leveraging a weak setting of the Domain variable.

Weakness: CWE-264

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

It affects 1 product.


Products: Ibm Lotus Sametime.

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

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

## Is CVE-2013-3985 being exploited?

There is no known exploitation of CVE-2013-3985 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2010-3398](https://insights.sbomify.com/CVE-2010-3398/): Other in n/a (critical 10.0)
- [CVE-2007-1784](https://insights.sbomify.com/CVE-2007-1784/): Code injection in n/a (critical 9.3)
- [CVE-2008-2499](https://insights.sbomify.com/CVE-2008-2499/): Memory corruption in n/a (high 7.5)
- [CVE-2011-1370](https://insights.sbomify.com/CVE-2011-1370/): Missing authorization in n/a (medium 5.0)
- [CVE-2013-3986](https://insights.sbomify.com/CVE-2013-3986/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3985 is a low-severity vulnerability in n/a, published on 9 Nov 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-3985 in the wild and no public exploit code.

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-3985/ (Markdown: https://insights.sbomify.com/CVE-2013-3985/index.md)
```

## Sources

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

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