# CVE-2021-28653: Weak cryptography in n/a

> Insecure key storage in Western Digital ArmorLock apps allows attackers to potentially access encrypted data on devices lacking biometric hardware.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8j44-9fww-xj8c

## What is CVE-2021-28653?

CVE-2021-28653 is a medium-severity vulnerability in n/a, published on 18 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The iOS and macOS apps before 1.4.1 for the Western Digital G-Technology ArmorLock NVMe SSD store keys insecurely. They choose a non-preferred storage mechanism if the device has Secure Enclave support but lacks biometric authentication hardware.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2021-28653?

It affects 1 product.


Products: Westerndigital Armorlock.

## How do I fix CVE-2021-28653?

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

## Is CVE-2021-28653 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28653 and fix it if it is affected.

What it is: CVE-2021-28653 is a medium-severity vulnerability in n/a, published on 18 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-28653 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-2021-28653/ (Markdown: https://insights.sbomify.com/CVE-2021-28653/index.md)
```

## Sources

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

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