# CVE-2020-28597: Weak cryptography in Epignosis

> Attackers can predict password reset tokens due to weak seeding, allowing them to take over arbitrary user accounts in EfrontPro.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 3 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9vx8-499f-5qv7

## What is CVE-2020-28597?

CVE-2020-28597 is a critical vulnerability in Epignosis, published on 3 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A predictable seed vulnerability exists in the password reset functionality of Epignosis EfrontPro 5.2.21. By predicting the seed it is possible to generate the correct password reset 1-time token. An attacker can visit the password reset supplying the password reset token to reset the password of an account of their choice.

Weakness: CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)), CWE-337 (Predictable Seed in Pseudo-Random Number Generator (PRNG))

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

It affects 1 product.


Products: Epignosishq Efront.

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

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

## Is CVE-2020-28597 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28597 is a critical vulnerability in Epignosis, published on 3 Mar 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-28597 in the wild and no public exploit code.

Affected product: Epignosis. 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-28597/ (Markdown: https://insights.sbomify.com/CVE-2020-28597/index.md)
```

## Sources

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

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