Open Quantum Safe liboqs 10.0 sign.c crypto_sign_signature risky encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Open Quantum Safe liboqs 10.0. Affected by this vulnerability is an unknown functionality of the file /pqcrystals-dilithium-standard_ml-dsa-44-ipd_avx2/sign.c. Such manipulation of the argument crypto_sign_signature leads to an unknown weakness. This vulnerability is documented as CVE-2024-31510. There is not any exploit available.
Details
A vulnerability was found in Open Quantum Safe liboqs 10.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /pqcrystals-dilithium-standard_ml-dsa-44-ipd_avx2/sign.c. The manipulation of the argument crypto_sign_signature with an unknown input leads to a unknown weakness. Using CWE to declare the problem leads to CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. Impacted is confidentiality, integrity, and availability. CVE summarizes:
An issue in Open Quantum Safe liboqs v.10.0 allows a remote attacker to escalate privileges via the crypto_sign_signature parameter in the /pqcrystals-dilithium-standard_ml-dsa-44-ipd_avx2/sign.c component.
This vulnerability is handled as CVE-2024-31510 since 04/05/2024. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1600.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Risky encryptionCWE: CWE-327 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/05/2024 🔍05/24/2024 🔍
05/24/2024 🔍
08/20/2025 🔍
Sources
Status: Not definedCVE: CVE-2024-31510 (🔍)
GCVE (CVE): GCVE-0-2024-31510
GCVE (VulDB): GCVE-100-266156
Entry
Created: 05/24/2024 17:30Updated: 08/20/2025 22:35
Changes: 05/24/2024 17:30 (50), 08/20/2025 22:35 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.