picoTCP/picoTCP-NG up to 1.7.0 DNS Packet pico_mdns.c pico_mdns_handle_data_as_answers_generic out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in picoTCP and picoTCP-NG up to 1.7.0. It has been classified as problematic. Affected by this issue is the function pico_mdns_handle_data_as_answers_generic of the file pico_mdns.c of the component DNS Packet Handler. Performing a manipulation results in out-of-bounds.
This vulnerability is identified as CVE-2020-24340. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in picoTCP and picoTCP-NG up to 1.7.0. It has been classified as problematic. This affects the function pico_mdns_handle_data_as_answers_generic of the file pico_mdns.c of the component DNS Packet Handler. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on availability.
The weakness was released 12/12/2020 as icsa-20-343-01. The advisory is shared at us-cert.cisa.gov. This vulnerability is uniquely identified as CVE-2020-24340. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
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: Out-of-boundsCWE: CWE-125 / CWE-119
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
08/13/2020 🔍12/12/2020 🔍
12/12/2020 🔍
12/16/2020 🔍
Sources
Advisory: icsa-20-343-01Status: Not defined
CVE: CVE-2020-24340 (🔍)
GCVE (CVE): GCVE-0-2020-24340
GCVE (VulDB): GCVE-100-166101
Entry
Created: 12/12/2020 07:33Updated: 12/16/2020 15:12
Changes: 12/12/2020 07:33 (38), 12/16/2020 15:10 (2), 12/16/2020 15:12 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.