# CVE-2014-0999: Information disclosure in n/a

> Remote attackers can hijack sessions and read sensitive data by exploiting session IDs exposed in email URLs via the Referrer header.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9rg4-v77r-32p7

## What is CVE-2014-0999?

CVE-2014-0999 is a medium-severity vulnerability in n/a, published on 2 Jun 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Sendio before 7.2.4 includes the session identifier in URLs in emails, which allows remote attackers to obtain sensitive information and hijack sessions by reading the jsessionid parameter in the Referrer HTTP header.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-0999?

It affects 1 product.


Products: Sendio Sendio.

## How do I fix CVE-2014-0999?

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

## Is CVE-2014-0999 being exploited?

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

Public exploit code:

- Sendio ESP - Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-10399](https://insights.sbomify.com/CVE-2016-10399/): Path traversal in n/a (high 7.5)
- [CVE-2014-8391](https://insights.sbomify.com/CVE-2014-8391/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0999 and fix it if it is affected.

What it is: CVE-2014-0999 is a medium-severity vulnerability in n/a, published on 2 Jun 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-0999 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-2014-0999/ (Markdown: https://insights.sbomify.com/CVE-2014-0999/index.md)
```

## Sources

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

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