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

> Remote attackers can sniff sensitive data from IBM Notes Traveler Android sessions due to missing HTTPS warnings, requiring user interaction to initiate the insecure connection.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j2fg-p5h6-6qcw

## What is CVE-2014-6130?

CVE-2014-6130 is a medium-severity vulnerability in n/a, published on 4 Nov 2014. 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 application before 9.0.1.3 for Android lacks a warning message during selection of an HTTP session, which makes it easier for remote attackers to obtain sensitive information by sniffing the network during a session in which the user had intended to use HTTPS.

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

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

It affects 1 product.


Products: Ibm Notes Traveler.

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

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

## Is CVE-2014-6130 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-6130 is a medium-severity vulnerability in n/a, published on 4 Nov 2014. 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-6130 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-6130/ (Markdown: https://insights.sbomify.com/CVE-2014-6130/index.md)
```

## Sources

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

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