# CVE-2020-9462: Information disclosure in n/a

> An attacker within RF range can intercept cleartext Wi-Fi credentials during device setup, allowing unauthorized access to the target's network.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hjxm-xx5r-w3mc

## What is CVE-2020-9462?

CVE-2020-9462 is a medium-severity vulnerability in n/a, published on 4 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in all Athom Homey and Homey Pro devices up to the current version 4.2.0. An attacker within RF range can obtain a cleartext copy of the network configuration of the device, including the Wi-Fi PSK, during device setup. Upon success, the attacker is able to further infiltrate the target's Wi-Fi networks.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 2 products.


Products: Homey Homey Firmware, Homey Homey Pro Firmware.

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

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

## Is CVE-2020-9462 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28952](https://insights.sbomify.com/CVE-2020-28952/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9462 is a medium-severity vulnerability in n/a, published on 4 Jun 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-9462 in the wild and no public exploit code.

Affected product: n/a. 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-9462/ (Markdown: https://insights.sbomify.com/CVE-2020-9462/index.md)
```

## Sources

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

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