virtualsquare picoTCP/picoTCP-NG modules/pico_fragments.c pico_fragments_reassemble double free
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in virtualsquare picoTCP and picoTCP-NG. Affected by this issue is the function pico_fragments_reassemble
of the file modules/pico_fragments.c. The manipulation leads to double free.
This vulnerability is handled as CVE-2021-33304. There is no exploit available.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as critical was found in virtualsquare picoTCP and picoTCP-NG (affected version not known). Affected by this vulnerability is the function pico_fragments_reassemble
of the file modules/pico_fragments.c. The manipulation with an unknown input leads to a double free vulnerability. The CWE definition for the vulnerability is CWE-415. The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Double Free vulnerability in virtualsquare picoTCP v1.7.0 and picoTCP-NG v2.1 in modules/pico_fragments.c in function pico_fragments_reassemble, allows attackers to execute arbitrary code.
The weakness was disclosed 02/16/2023. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2021-33304 since 05/20/2021. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: 🔍
Exploiting
Class: Double freeCWE: CWE-415 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
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
05/20/2021 🔍02/16/2023 🔍
02/16/2023 🔍
03/16/2023 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2021-33304 (🔍)
GCVE (CVE): GCVE-0-2021-33304
GCVE (VulDB): GCVE-100-221167
Entry
Created: 02/16/2023 08:23Updated: 03/16/2023 12:25
Changes: 02/16/2023 08:23 (37), 03/16/2023 12:25 (11)
Complete: 🔍
Cache ID: 216:976:103
No comments yet. Languages: en.
Please log in to comment.