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

> Percona XtraDB Cluster uses a static transition key for SST processes, allowing attackers to bypass authentication and access data.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4r6g-prvv-3gp3

## What is CVE-2020-10996?

CVE-2020-10996 is a high-severity vulnerability in n/a, published on 27 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Percona XtraDB Cluster before 5.7.28-31.41.2. A bundled script inadvertently sets a static transition_key for SST processes in place of the random key expected.

Weakness: CWE-838 (Inappropriate Encoding for Output Context), CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Percona Xtradb Cluster.

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

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

## Is CVE-2020-10996 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10996 is a high-severity vulnerability in n/a, published on 27 Apr 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-10996 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-10996/ (Markdown: https://insights.sbomify.com/CVE-2020-10996/index.md)
```

## Sources

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

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