# CVE-2016-6799: Information Exposure in cordova-android


- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gwpf-62xp-vrg6

## What is CVE-2016-6799?

CVE-2016-6799 is a high-severity vulnerability in Apache Cordova Android, published on 9 May 2017. 

### Official description

Product: Apache Cordova Android 5.2.2 and earlier. The application calls methods of the Log class. Messages passed to these methods (Log.v(), Log.d(), Log.i(), Log.w(), and Log.e()) are stored in a series of circular buffers on the device. By default, a maximum of four 16 KB rotated logs are kept in addition to the current log. The logged data can be read using Logcat on the device. When using platforms prior to Android 4.1 (Jelly Bean), the log data is not sandboxed per application; any application installed on the device has the capability to read data logged by other applications.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

2 open source packages ship an affected version, including cordova-android. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cordova-android` | npm | All versions | 6.0.0 |
| `cordova-android` | npm | All versions | 6.0.0 |

Products: Apache Cordova.

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

Upgrade cordova-android to 6.0.0 or later.

## Is CVE-2016-6799 being exploited?

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

## Other vulnerabilities in Apache Cordova Android

- [CVE-2021-21315](https://insights.sbomify.com/CVE-2021-21315/): System Information Library for Node.JS Command Injection (high 7.1, exploited in the wild)
- [CVE-2014-0073](https://insights.sbomify.com/CVE-2014-0073/): Cross-site scripting in n/a (critical 9.8)
- [CVE-2014-0072](https://insights.sbomify.com/CVE-2014-0072/): Security feature bypass in n/a (high 7.5)
- [CVE-2017-3160](https://insights.sbomify.com/CVE-2017-3160/): Supply chain in Apache Cordova Android (high 7.4)
- [CVE-2014-3500](https://insights.sbomify.com/CVE-2014-3500/): Other in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6799 is a high-severity vulnerability in Apache Cordova Android, published on 9 May 2017. 
Exploitation: There is no known exploitation of CVE-2016-6799 in the wild and no public exploit code.

Affected packages and fixed versions:
- cordova-android (npm): affected all versions; fixed in 6.0.0
- cordova-android (npm): affected all versions; fixed in 6.0.0

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-6799/ (Markdown: https://insights.sbomify.com/CVE-2016-6799/index.md)
```

## Sources

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

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