CVE-2019-25605
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2019-25605 is a high-severity Improper Authorization of Index Containing Sensitive Information (CWE-612) vulnerability in Google (inferred from references). Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Information Repositories (T1213); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
EquityPandit 1.0, an Android application, suffers from CVE-2019-25605, an insecure logging vulnerability classified under CWE-612. The issue involves the app logging plaintext user passwords to developer console logs during the forgot password function, making them accessible via the Android Debug Bridge (ADB). This flaw has a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating high confidentiality impact with no requirements for privileges or user interaction.
Any remote attacker can exploit this vulnerability by using the adb logcat command to capture the exposed logs and extract sensitive user credentials, such as plaintext passwords. Successful exploitation reveals account credentials for affected users, potentially enabling unauthorized access to user accounts without needing physical device access, authentication, or user involvement, as reflected in the CVSS vector.
Advisories and related resources, including the Vulncheck advisory on EquityPandit insecure logging, an Exploit-DB proof-of-concept (exploit 46933), and the app's Google Play Store listing, document the issue but do not specify patches or mitigations in the available details. Security practitioners should review these references for reproduction steps and verify if updated app versions address the logging flaw.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2019-19952
Vulnerability Data
EquityPandit 1.0 contains an insecure logging vulnerability that allows attackers to capture sensitive user credentials by accessing developer console logs via Android Debug Bridge. Attackers can use adb logcat to extract plaintext passwords logged during the forgot password function, exposing…
more
user account credentials.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly enforces authorization checks on the search index so that only users permitted to view the original documents can access indexed content.
AC-6 limits privileges so that fewer accounts can reach the index, reducing the chance that unauthorized actors obtain sensitive indexed data.
AC-16 associates sensitivity attributes with data, enabling the index to inherit and enforce the same access restrictions as the source documents.
AC-4 enforces information-flow rules that can stop sensitive data from being reachable through an improperly authorized index.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Directly enforces authorization policy and least privilege for access to sensitive data including indexes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Classification helps identify what must be protected but does not enforce index access limits.
Access control policies directly limit who can query or view the index.
Managing access rights ensures only authorized users can reach indexed sensitive content.
Data leakage prevention can block unauthorized index exposure but is supplementary.
Privileged access rights may be used to enforce index restrictions but are not the primary control.
Information access restriction is the technical mechanism that prevents unauthorized index queries.