CVE-2020-4060
"LoRa Basics Station Use After Free Vulnerability"
Description
In LoRa Basics Station before 2.0.4, there is a Use After Free vulnerability that leads to memory corruption. This bug is triggered on 32-bit machines when the CUPS server responds with a message (https://doc.sm.tc/station/cupsproto.html#http-post-response) where the signature length is larger than 2 GByte (never happens in practice), or the response is crafted specifically to trigger this issue (i.e. the length signature field indicates a value larger than (2**31)-1 although the signature actually does not contain that much data). In such a scenario, on 32 bit machines, Basic Station would execute a code path, where a piece of memory is accessed after it has been freed, causing the process to crash and restarted again. The CUPS transaction is typically mutually authenticated over TLS. Therefore, in order to trigger this vulnerability, the attacker would have to gain access to the CUPS server first. If the user chose to operate without authentication over TLS but yet is concerned about this vulnerability, one possible workaround is to enable TLS authentication. This has been fixed in 2.0.4.
INFO
Published Date :
June 22, 2020, 4:15 p.m.
Last Modified :
July 1, 2020, 2:31 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
1.4
Exploitability Score :
3.1
Public PoC/Exploit Available at Github
CVE-2020-4060 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2020-4060.
| URL | Resource |
|---|---|
| https://github.com/lorabasics/basicstation/security/advisories/GHSA-v9ph-r496-4m2j | Mitigation Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Some Vulnerability in the some protocol are collected.
vulnerabilities protocol security
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2020-4060 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2020-4060 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Jul. 01, 2020
Action Type Old Value New Value Added CVSS V2 NIST (AV:N/AC:L/Au:S/C:N/I:N/A:P) Added CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L Changed Reference Type https://github.com/lorabasics/basicstation/security/advisories/GHSA-v9ph-r496-4m2j No Types Assigned https://github.com/lorabasics/basicstation/security/advisories/GHSA-v9ph-r496-4m2j Mitigation, Third Party Advisory Added CPE Configuration OR *cpe:2.3:a:semtech:lora_basics_station:*:*:*:*:*:*:*:* versions up to (excluding) 2.0.4
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2020-4060 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2020-4060
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.07 }} 0.00%
score
0.29363
percentile