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

> Eaton's Secure Connect mobile app stores login credentials in logcat, allowing malicious apps or unauthorized users to harvest them and take over accounts.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v536-97c8-3vw5

## What is CVE-2020-6653?

CVE-2020-6653 is a low-severity vulnerability in Eaton Secure Connect Mobile App, published on 12 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2020-6653?

It affects 1 product.


Products: Eaton Secureconnect.

## How do I fix CVE-2020-6653?

No fix has been published for CVE-2020-6653 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-6653 being exploited?

There is no known exploitation of CVE-2020-6653 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6653 and fix it if it is affected.

What it is: CVE-2020-6653 is a low-severity vulnerability in Eaton Secure Connect Mobile App, published on 12 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6653 in the wild and no public exploit code.

Affected product: Eaton Secure Connect Mobile App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-6653/ (Markdown: https://insights.sbomify.com/CVE-2020-6653/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-6653
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-6653
- OSV: https://osv.dev/vulnerability/CVE-2020-6653

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-6653/
Summaries are generated and may contain mistakes; the official description above is the record.