# CVE-2020-24030: Weak cryptography in n/a

> Weak token expiration in ForLogic Qualiex allows remote unauthenticated privilege escalation and sensitive data access via token reuse.

- **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:** 2 Sep 2020
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-w553-m7x7-p3hj

## What is CVE-2020-24030?

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

### Official description

ForLogic Qualiex v1 and v3 has weak token expiration. This allows remote unauthenticated privilege escalation and access to sensitive data via token reuse. NOTE: as of 2025-10-14, the Supplier's perspective is that this is "not exploitable in the current implementation. Tokens are properly expired, invalidated, and bound to session context. Attempts to alter the token payload to extend its validity do not affect server-side validation."

Weakness: CWE-672 (Operation on a Resource after Expiration or Release)

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

It affects 1 product.


Products: Forlogic Qualiex.

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

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

## Is CVE-2020-24030 being exploited?

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

Public exploit code:

- https://github.com/underprotection/CVE-2020-24030 (github_poc): https://github.com/underprotection/CVE-2020-24030
- https://github.com/RedTeamBrasil/CVE-2020-24030 (github_poc): https://github.com/RedTeamBrasil/CVE-2020-24030

## Other vulnerabilities in n/a

- [CVE-2020-24029](https://insights.sbomify.com/CVE-2020-24029/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-24028](https://insights.sbomify.com/CVE-2020-24028/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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