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

> Remote attackers can capture credentials via phishing attacks exploiting unrestricted automatic configuration executions in the IBM Notes Traveler Companion app.

- **Severity:** Medium 4.3 (`AV:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cj4w-9xfh-m2w2

## What is CVE-2014-8921?

CVE-2014-8921 is a medium-severity vulnerability in n/a, published on 2 Mar 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The IBM Notes Traveler Companion application 1.0 and 1.1 before 201411010515 for Window Phone, as distributed in IBM Notes Traveler 9.0.1, does not properly restrict the number of executions of the automatic configuration option, which makes it easier for remote attackers to capture credentials by conducting a phishing attack involving an encrypted e-mail message.

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

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

It affects 1 product.


Products: Ibm Notes Traveler Companion.

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

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

## Is CVE-2014-8921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8921 is a medium-severity vulnerability in n/a, published on 2 Mar 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-8921 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-2014-8921/ (Markdown: https://insights.sbomify.com/CVE-2014-8921/index.md)
```

## Sources

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

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