# CVE-2023-24025: Information disclosure in n/a

> Attackers can leak intermediate data via side-channels to forge digital signatures in the PQClean library, compromising cryptographic integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-xrr5-3hrr-35jx

## What is CVE-2023-24025?

CVE-2023-24025 is a high-severity vulnerability in n/a, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CRYSTALS-DILITHIUM (in Post-Quantum Cryptography Selected Algorithms 2022) in PQClean d03da30 may allow universal forgeries of digital signatures via a template side-channel attack because of intermediate data leakage of one vector.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2023-24025?

It affects 1 product.


Products: Pqclean Project Pqclean.

## How do I fix CVE-2023-24025?

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

## Is CVE-2023-24025 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24025 and fix it if it is affected.

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

## Sources

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

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