Crypto++ up to 8.6.0 Private Key MakePublicKey timing discrepancy ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Crypto++ up to 8.6.0. This affects the function MakePublicKey of the component Private Key Handler. The manipulation results in timing discrepancy.
This vulnerability is cataloged as CVE-2021-43398. There is no exploit available.
The presence of this vulnerability remains uncertain at this time.
Details
A vulnerability classified as problematic has been found in Crypto++ up to 8.6.0. Affected is the function MakePublicKey of the component Private Key Handler. The manipulation with an unknown input leads to a timing discrepancy vulnerability. CWE is classifying the issue as CWE-208. Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not. This is going to have an impact on confidentiality.
The weakness was shared 11/05/2021 as 1080. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2021-43398 since 11/04/2021. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
The real existence of this vulnerability is still doubted at the moment.
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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.9VulDB Meta Temp Score: 3.9
VulDB Base Score: 2.6
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Timing discrepancyCWE: CWE-208 / CWE-203 / CWE-200
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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
11/04/2021 🔍11/05/2021 🔍
11/05/2021 🔍
08/04/2024 🔍
Sources
Advisory: 1080Status: Confirmed
Disputed: 🔍
CVE: CVE-2021-43398 (🔍)
GCVE (CVE): GCVE-0-2021-43398
GCVE (VulDB): GCVE-100-186084
Entry
Created: 11/05/2021 10:53Updated: 08/04/2024 07:09
Changes: 11/05/2021 10:53 (37), 11/09/2021 21:31 (1), 08/04/2024 07:09 (35)
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.