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

> A hardcoded backdoor password allows attackers to bypass authentication and gain unauthorized access to the Epikur server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 5 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q4x8-w6fw-v9hh

## What is CVE-2020-10539?

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

### Official description

An issue was discovered in Epikur before 20.1.1. The Epikur server contains the checkPasswort() function that, upon user login, checks the submitted password against the user password's MD5 hash stored in the database. It is also compared to a second MD5 hash, which is the same for every user (aka a "Backdoor Password" of 3p1kursupport). If the submitted password matches either one, access is granted.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Epikur Epikur.

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

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

## Is CVE-2020-10539 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10537](https://insights.sbomify.com/CVE-2020-10537/): Auth bypass in n/a (high 7.8)
- [CVE-2020-10538](https://insights.sbomify.com/CVE-2020-10538/): Weak cryptography in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10539 is a critical vulnerability in n/a, published on 5 Feb 2021. 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-10539 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-10539/ (Markdown: https://insights.sbomify.com/CVE-2020-10539/index.md)
```

## Sources

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

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