CVE-2018-6599

{"containers": {"cna": {"affected": [{"product": "n/a", "vendor": "n/a", "versions": [{"status": "affected", "version": "n/a"}]}], "datePublic": "2018-08-14T00:00:00.000Z", "descriptions": [{"lang": "en", "value": "An issue was discovered on Orbic Wonder Orbic/RC555L/RC555L:7.1.2/N2G47H/329100b:user/release-keys devices, allowing attackers to obtain sensitive information (such as text-message content) by reading a copy of the Android log on the SD card. The system-wide Android logs are not directly available to third-party apps since they tend to contain sensitive data. Third-party apps can read from the log but only the log messages that the app itself has written. Certain apps can leak data to the Android log due to not sanitizing log messages, which is in an insecure programming practice. Pre-installed system apps and apps that are signed with the framework key can read from the system-wide Android log. We found a pre-installed app on the Orbic Wonder that when started via an Intent will write the Android log to the SD card, also known as external storage, via com.ckt.mmitest.MmiMainActivity. Any app that requests the READ_EXTERNAL_STORAGE permission can read from the SD card. Therefore, a local app on the device can quickly start a specific component in the pre-installed system app to have the Android log written to the SD card. Therefore, any app co-located on the device with the READ_EXTERNAL_STORAGE permission can obtain the data contained within the Android log and continually monitor it and mine the log for relevant data. In addition, the default messaging app (com.android.mms) writes the body of sent and received text messages to the Android log, as well as the recipient phone number for sent text messages and the sending phone number for received text messages. In addition, any call data contains phone numbers for sent and received calls."}], "problemTypes": [{"descriptions": [{"description": "n/a", "lang": "en", "type": "text"}]}], "providerMetadata": {"dateUpdated": "2018-08-29T18:57:01.000Z", "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca", "shortName": "mitre"}, "references": [{"tags": ["x_refsource_MISC"], "url": "https://www.kryptowire.com/portal/android-firmware-defcon-2018/"}], "x_legacyV4Record": {"CVE_data_meta": {"ASSIGNER": "cve@mitre.org", "ID": "CVE-2018-6599", "STATE": "PUBLIC"}, "affects": {"vendor": {"vendor_data": [{"product": {"product_data": [{"product_name": "n/a", "version": {"version_data": [{"version_value": "n/a"}]}}]}, "vendor_name": "n/a"}]}}, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": {"description_data": [{"lang": "eng", "value": "An issue was discovered on Orbic Wonder Orbic/RC555L/RC555L:7.1.2/N2G47H/329100b:user/release-keys devices, allowing attackers to obtain sensitive information (such as text-message content) by reading a copy of the Android log on the SD card. The system-wide Android logs are not directly available to third-party apps since they tend to contain sensitive data. Third-party apps can read from the log but only the log messages that the app itself has written. Certain apps can leak data to the Android log due to not sanitizing log messages, which is in an insecure programming practice. Pre-installed system apps and apps that are signed with the framework key can read from the system-wide Android log. We found a pre-installed app on the Orbic Wonder that when started via an Intent will write the Android log to the SD card, also known as external storage, via com.ckt.mmitest.MmiMainActivity. Any app that requests the READ_EXTERNAL_STORAGE permission can read from the SD card. Therefore, a local app on the device can quickly start a specific component in the pre-installed system app to have the Android log written to the SD card. Therefore, any app co-located on the device with the READ_EXTERNAL_STORAGE permission can obtain the data contained within the Android log and continually monitor it and mine the log for relevant data. In addition, the default messaging app (com.android.mms) writes the body of sent and received text messages to the Android log, as well as the recipient phone number for sent text messages and the sending phone number for received text messages. In addition, any call data contains phone numbers for sent and received calls."}]}, "problemtype": {"problemtype_data": [{"description": [{"lang": "eng", "value": "n/a"}]}]}, "references": {"reference_data": [{"name": "https://www.kryptowire.com/portal/android-firmware-defcon-2018/", "refsource": "MISC", "url": "https://www.kryptowire.com/portal/android-firmware-defcon-2018/"}]}}}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-05T06:10:10.849Z"}, "title": "CVE Program Container", "references": [{"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://www.kryptowire.com/portal/android-firmware-defcon-2018/"}]}]}, "cveMetadata": {"assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca", "assignerShortName": "mitre", "cveId": "CVE-2018-6599", "datePublished": "2018-08-29T19:00:00.000Z", "dateReserved": "2018-02-03T00:00:00.000Z", "dateUpdated": "2024-08-05T06:10:10.849Z", "state": "PUBLISHED"}, "dataType": "CVE_RECORD", "dataVersion": "5.1"}

{}

{"affected": [{"affectedData": [{"product": "n/a", "vendor": "n/a", "versions": [{"status": "affected", "version": "n/a"}]}], "source": "cve@mitre.org"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:orbic:wonder_rc555l_firmware:7.1:*:*:*:*:*:*:*", "matchCriteriaId": "1F4F25BE-8E8F-4D94-A70C-316F9A772238", "vulnerable": true}, {"criteria": "cpe:2.3:o:orbic:wonder_rc555l_firmware:7.1.2:*:*:*:*:*:*:*", "matchCriteriaId": "3F31A829-FB63-417D-AE7D-31BE9E03A4D8", "vulnerable": true}], "negate": false, "operator": "OR"}, {"cpeMatch": [{"criteria": "cpe:2.3:h:orbic:wonder_rc555l:-:*:*:*:*:*:*:*", "matchCriteriaId": "9FEBA4B7-742F-4914-BD59-C657CEC22DD7", "vulnerable": false}], "negate": false, "operator": "OR"}], "operator": "AND"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "An issue was discovered on Orbic Wonder Orbic/RC555L/RC555L:7.1.2/N2G47H/329100b:user/release-keys devices, allowing attackers to obtain sensitive information (such as text-message content) by reading a copy of the Android log on the SD card. The system-wide Android logs are not directly available to third-party apps since they tend to contain sensitive data. Third-party apps can read from the log but only the log messages that the app itself has written. Certain apps can leak data to the Android log due to not sanitizing log messages, which is in an insecure programming practice. Pre-installed system apps and apps that are signed with the framework key can read from the system-wide Android log. We found a pre-installed app on the Orbic Wonder that when started via an Intent will write the Android log to the SD card, also known as external storage, via com.ckt.mmitest.MmiMainActivity. Any app that requests the READ_EXTERNAL_STORAGE permission can read from the SD card. Therefore, a local app on the device can quickly start a specific component in the pre-installed system app to have the Android log written to the SD card. Therefore, any app co-located on the device with the READ_EXTERNAL_STORAGE permission can obtain the data contained within the Android log and continually monitor it and mine the log for relevant data. In addition, the default messaging app (com.android.mms) writes the body of sent and received text messages to the Android log, as well as the recipient phone number for sent text messages and the sending phone number for received text messages. In addition, any call data contains phone numbers for sent and received calls."}, {"lang": "es", "value": "Se ha descubierto un problema en dispositivos Orbic Wonder Orbic/RC555L/RC555L:7.1.2/N2G47H/329100b:user/release-key que permite que los atacantes obtengan informaci\u00f3n sensible (como el contenido de mensajes de texto) mediante la lectura del registro de Android en la tarjeta SD. Los registros de Android del sistema no est\u00e1n directamente disponibles a aplicaciones de terceros, ya que suelen contener datos sensibles. Las aplicaciones de terceros pueden leer desde el registro, pero solo aquellos registros que hayan sido escritos por la propia aplicaci\u00f3n. Ciertas aplicaciones pueden filtrar datos al registro de Android debido a que no se sanean los mensajes de registro, lo que supone una pr\u00e1ctica insegura de programaci\u00f3n. Las aplicaciones preinstaladas del sistema y las aplicaciones que est\u00e1n firmadas con la clave del framework pueden leer del registro de Android del sistema. Se ha encontrado una aplicaci\u00f3n preinstalada en Orbic Wonder que, al iniciarse mediante un Intent, escribir\u00e1 el registro de Android en la tarjeta SD, tambi\u00e9n conocida como almacenamiento externo, por medio de com.ckt.mmitest.MmiMainActivity. Cualquier aplicaci\u00f3n que solicita el permiso READ_EXTERNAL_STORAGE puede leer desde la tarjeta SD. Por lo tanto, una aplicaci\u00f3n local puede lanzar r\u00e1pidamente un componente espec\u00edfico en la aplicaci\u00f3n preinstalada del sistema para hacer que el registro de Android se escriba en la tarjeta SD. Por lo tanto, cualquier aplicaci\u00f3n colocada en el dispositivo con el permiso READ_EXTERNAL_STORAGE puede obtener los datos contenidos en el registro de Android y monitorizarlo continuamente y minarlo para buscar datos relevantes. Adem\u00e1s, la aplicaci\u00f3n de mensajer\u00eda por defecto (com.android.mms) escribe el cuerpo de los mensajes de texto enviados y recibidos al registro de Android, as\u00ed como al n\u00famero de tel\u00e9fono del destinatario para los mensajes enviados y el n\u00famero de tel\u00e9fono del remitente para los mensajes de texto recibidos. Aparte, cualquier dato de llamadas contiene n\u00fameros de tel\u00e9fono para las llamadas realizadas y recibidas."}], "id": "CVE-2018-6599", "lastModified": "2026-06-17T02:02:04.887", "metrics": {"cvssMetricV2": [{"acInsufInfo": false, "baseSeverity": "LOW", "cvssData": {"accessComplexity": "LOW", "accessVector": "LOCAL", "authentication": "NONE", "availabilityImpact": "NONE", "baseScore": 2.1, "confidentialityImpact": "PARTIAL", "integrityImpact": "NONE", "vectorString": "AV:L/AC:L/Au:N/C:P/I:N/A:N", "version": "2.0"}, "exploitabilityScore": 3.9, "impactScore": 2.9, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "source": "nvd@nist.gov", "type": "Primary", "userInteractionRequired": false}], "cvssMetricV30": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "NONE", "baseScore": 5.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.0"}, "exploitabilityScore": 1.8, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary"}]}, "published": "2018-08-29T19:29:01.187", "references": [{"source": "cve@mitre.org", "tags": ["Third Party Advisory"], "url": "https://www.kryptowire.com/portal/android-firmware-defcon-2018/"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Third Party Advisory"], "url": "https://www.kryptowire.com/portal/android-firmware-defcon-2018/"}], "sourceIdentifier": "cve@mitre.org", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-532"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{}

{}