# CVE-2016-1185: Information disclosure in n/a

> Attackers can discover authentication tokens via a crafted application, potentially leading to account takeover in the kintone mobile app.

- **Severity:** Low 2.5 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-64p3-6rw8-rfch

## What is CVE-2016-1185?

CVE-2016-1185 is a low-severity vulnerability in n/a, published on 25 Apr 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Cybozu kintone mobile application 1.x before 1.0.6 for Android allows attackers to discover an authentication token via a crafted application.

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

## Which versions are affected by CVE-2016-1185?

It affects 1 product.


Products: Cybozu Kintone.

## How do I fix CVE-2016-1185?

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

## Is CVE-2016-1185 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-7816](https://insights.sbomify.com/CVE-2016-7816/): Weak cryptography in kintone mobile for Android (medium 5.9)
- [CVE-2016-1186](https://insights.sbomify.com/CVE-2016-1186/): Security feature bypass in n/a (medium 5.9)
- [CVE-2020-5573](https://insights.sbomify.com/CVE-2020-5573/): Information disclosure in Android App 'kintone mobile for Android' (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1185 and fix it if it is affected.

What it is: CVE-2016-1185 is a low-severity vulnerability in n/a, published on 25 Apr 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-1185 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-2016-1185/ (Markdown: https://insights.sbomify.com/CVE-2016-1185/index.md)
```

## Sources

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

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