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

> Attackers can extract encryption keys from memory to sign malicious boot stages, compromising the integrity of the boot process in AT91bootstrap.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-233h-674c-hxmw

## What is CVE-2020-11684?

CVE-2020-11684 is a critical vulnerability in n/a, published on 14 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AT91bootstrap before 3.9.2 does not properly wipe encryption and authentication keys from memory before passing control to a less privileged software component. This can be exploited to disclose these keys and subsequently encrypt and sign the next boot stage (such as the bootloader).

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

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

It affects 1 product.


Products: Linux4sam At91bootstrap.

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

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

## Is CVE-2020-11684 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11683](https://insights.sbomify.com/CVE-2020-11683/): Information disclosure in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11684 is a critical vulnerability in n/a, published on 14 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11684 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-11684/ (Markdown: https://insights.sbomify.com/CVE-2020-11684/index.md)
```

## Sources

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

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