VYPR
Unrated severityNVD Advisory· Published Oct 15, 2019· Updated Aug 5, 2024

CVE-2019-17396

CVE-2019-17396

Description

PowerSchool Mobile 1.1.8 logs username and password in Android logcat during authentication, exposing credentials to attackers.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

PowerSchool Mobile 1.1.8 logs username and password in Android logcat during authentication, exposing credentials to attackers.

Vulnerability

PowerSchool Mobile version 1.1.8 for Android logs the username and password in plaintext within the authentication request XML, which is written to the system log (logcat). This occurs during the login process when the app sends a SOAP request to the server. The log entry contains the full request XML, including ` and ` elements with the user's credentials.[1]

Exploitation

An attacker with access to the device's logcat output can retrieve the credentials. On Android versions prior to Jelly Bean (API level 16), any installed app can read logcat without special permissions. On later versions, the attacker would need either physical access to the device, a compromised app with READ_LOGS permission (deprecated but still effective on some devices), or the ability to run adb logcat via USB debugging. The attacker can filter for 'password' in logcat output to locate the credentials.[1]

Impact

Successful exploitation allows the attacker to obtain the victim's PowerSchool username and password. This can lead to unauthorized access to the PowerSchool portal, potentially exposing sensitive student and school information depending on the user's privileges.

Mitigation

The vendor was notified and stated a fix would be released soon. As of the publication date (2019-10-15), no patched version was available. Users should avoid using the app on untrusted devices or with USB debugging enabled, and logcat output should be monitored for exposure. The app may have been updated since; checking the current version on the Google Play Store is recommended.[1]

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.