LiveActive security incident?Get immediate response
CVE Record

CVE-2016-6799: Product: Apache Cordova Android 5.2.2 and earlier.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE concerns Apache Cordova Android 5.2.2 and earlier logging application messages to Android device logs. On Android versions before 4.1, those logs were not isolated per app, so another installed app could read data a Cordova app logged. Business risk depends on whether sensitive or internal data was written to logs and whether users run very old Android versions. Exposure is most likely in legacy Cordova Android apps built with version 5.2.2 or earlier, especially if they logged credentials, tokens, internal system information, or user data and ran on Android versions before 4.1. Treat as a legacy mobile data-exposure issue. Prioritize if the organization still supports old Android devices or legacy Cordova builds that may log sensitive data. Otherwise, handle through mobile app modernization and secure logging hygiene. Mitigation focus: Inventory Cordova Android apps using version 5.2.2 or earlier.; Check Apache Cordova Android guidance for fixed versions or vendor-recommended remediation.; Remove sensitive, internal, authentication, or user data from application logs..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-6799 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Cordova Android5.2.2 and earlierListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.