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

> Attackers can read sensitive user IDs, meeting details, and authentication tokens from system logs in the Citrix GoToMeeting Android app.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j6mp-9cfw-7j4j

## What is CVE-2014-1664?

CVE-2014-1664 is a medium-severity vulnerability in n/a, published on 26 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Citrix GoToMeeting application 5.0.799.1238 for Android logs HTTP requests containing sensitive information, which allows attackers to obtain user IDs, meeting details, and authentication tokens via an application that reads the system log file.

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

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

It affects 1 product.


Products: Citrix Gotomeeting.

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

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

## Is CVE-2014-1664 being exploited?

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

Public exploit code:

- GoToMeeting for Android - Multiple Local Information Disclosure Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-1664 is a medium-severity vulnerability in n/a, published on 26 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-1664 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-1664/ (Markdown: https://insights.sbomify.com/CVE-2014-1664/index.md)
```

## Sources

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

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