# CVE-2020-12789: Hardcoded credentials in n/a

> Hardcoded keys in Microchip ATSAMA5 Secure Monitor allow attackers to bypass authentication and execute arbitrary secure applets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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-fhhq-g694-vvfc

## What is CVE-2020-12789?

CVE-2020-12789 is a high-severity 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

The Secure Monitor in Microchip Atmel ATSAMA5 products use a hardcoded key to encrypt and authenticate secure applets.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 76 products.


Products: Microchip Atsama5d21c-Cu Firmware, Microchip Atsama5d21c-Cur Firmware, Microchip Atsama5d225c-D1m-Cur Firmware, Microchip Atsama5d22c-Cn Firmware, Microchip Atsama5d22c-Cnr Firmware, Microchip Atsama5d22c-Cu Firmware, Microchip Atsama5d22c-Cur Firmware, Microchip Atsama5d23c-Cn Firmware, Microchip Atsama5d23c-Cnr Firmware, Microchip Atsama5d23c-Cu Firmware, Microchip Atsama5d23c-Cur Firmware, Microchip Atsama5d24c-Cu Firmware, Microchip Atsama5d24c-Cuf Firmware, Microchip Atsama5d24c-Cur Firmware, Microchip Atsama5d26c-Cn Firmware, Microchip Atsama5d26c-Cnr Firmware, Microchip Atsama5d26c-Cu Firmware, Microchip Atsama5d26c-Cur Firmware, Microchip Atsama5d27-Som1 Firmware, Microchip Atsama5d27-Wlsom1 Firmware and 56 more.

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

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

## Is CVE-2020-12789 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12787](https://insights.sbomify.com/CVE-2020-12787/): Security feature bypass in n/a (high 7.5)
- [CVE-2020-12788](https://insights.sbomify.com/CVE-2020-12788/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12789 is a high-severity 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-12789 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-12789/ (Markdown: https://insights.sbomify.com/CVE-2020-12789/index.md)
```

## Sources

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

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