CVE-2023-24025
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCRYSTALS-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCRYSTALS-DILITHIUM signature scheme implementation in PQClean library (d03da30) contains a side-channel vulnerability where intermediate data leakage of one vector enables a template side-channel attack allowing universal signature forgeries. An attacker with the ability to perform template side-channel measurements can recover sufficient information to forge valid signatures for arbitrary messages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate PQClean library in your environmentSearch project directories, dependencies, and build configurations for PQClean source files (dilitheum*.c, dilithium*.h) or library referencesAffected if PQClean library files or package dependencies are present in your codebase or deployed binaries
-
Identify CRYSTALS-DILITHIUM signature usageSearch source code and compiled binaries for dilithium_sign, dilithium_verify function calls or include statements for dilithium.hAffected if Your application or service uses CRYSTALS-DILITHIUM signature functions from the PQClean library
-
Determine the PQClean version or commitCheck the git commit hash in your PQClean installation folder (look for .git directory), or search for version strings in header filesAffected if The commit is d03da30 or any version prior to the CVE-2023-24025 patch (all versions are currently affected)
-
Check if side-channel attack is feasible in your deploymentEvaluate whether an attacker could physically access or place measurement probes near the machine performing DILITHIUM signing operationsAffected if The system performing signatures is physically accessible or subject to electromagnetic/proximity measurements
If your environment uses PQClean's CRYSTALS-DILITHIUM implementation and an attacker can perform template side-channel measurements against signing operations, you are affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate PQClean to a patched version that addresses the template side-channel leakage. Review deployed systems using this library and consider implementing additional side-channel countermeasures such as constant-time implementations and hardware-based attack prevention.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-24025 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data