Process crash via freed CUPS signature pointer
Published Jun 22, 2020 · Updated Aug 4, 2024
Use-after-free in cups_update_info in Semtech LoRa Basics Station before 2.0.4 allows attackers controlling CUPS replies to crash Station. On 32-bit builds, cups_update_info accepts a signature length above 2^31-1, frees the signature buffer, and then accesses the stale pointer. The condition normally requires control of the mutually authenticated CUPS server, and successful exploitation restarts the process.
Summary
What happened
Use-after-free in cups_update_info in Semtech LoRa Basics Station before 2.0.4 allows attackers controlling CUPS replies to crash Station. On 32-bit builds, cups_update_info accepts a signature length above 2^31-1, frees the signature buffer, and then accesses the stale pointer. The condition normally requires control of the mutually authenticated CUPS server, and successful exploitation restarts the process.
The record
- CVE
- CVE-2020-4060
- Published
- Jun 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Semtech
- Product
- LoRa Basics Station
- Classifications
- CWE-416, T1489
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo