| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in picoquic. It has been rated as problematic. Affected by this issue is the function picoquic_decode_frames/picoquic_decode_stream_frame of the component QUIC Frame Handler. The manipulation leads to infinite loop.
This vulnerability is traded as CVE-2020-24944. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability was found in picoquic (version unknown). It has been rated as problematic. This issue affects the function picoquic_decode_frames/picoquic_decode_stream_frame of the component QUIC Frame Handler. The manipulation with an unknown input leads to a infinite loop vulnerability. Using CWE to declare the problem leads to CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Impacted is availability.
The weakness was shared 02/09/2021. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2020-24944. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Infinite loopCWE: CWE-835 / CWE-404
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
08/28/2020 🔍02/09/2021 🔍
02/09/2021 🔍
02/25/2021 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2020-24944 (🔍)
GCVE (CVE): GCVE-0-2020-24944
GCVE (VulDB): GCVE-100-169379
Entry
Created: 02/09/2021 08:19Updated: 02/25/2021 11:45
Changes: 02/09/2021 08:19 (36), 02/25/2021 11:39 (5), 02/25/2021 11:45 (18)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.