dbcve.org
Lora Basics StationApplication · Semtech

CVE-2020-4060

MEDIUM · 5.0 CVSS v3.1 Published 2020-06-22
Fix available
A fix is available. Upgrade to 2.0.4 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

LoRa Basics Station before 2.0.4 contains a Use After Free vulnerability on 32-bit machines. When the CUPS server responds with a crafted message where the signature length field indicates a value larger than (2**31)-1 but actual signature data doesn't match, memory is accessed after being freed, causing crash and restart.

MitigationUpgrade LoRa Basics Station to version 2.0.4 or later. As a workaround, enable TLS authentication on CUPS transactions to prevent attackers from intercepting or tampering with server responses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Lora Basics StationApplication
Affected:< 2.0.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the LoRa Basics Station installation
    Identify where the Basics Station binary or service is installed. Common locations: /usr/local/bin/station, /opt/lora/station, or check running processes for 'station' process.
    Affected if LoRa Basics Station is not found or the binary/service is absent - not applicable.
  2. Determine installed version of Basics Station
    Run 'station --version' or check the binary version information. Compare the version number to 2.0.4.
    Affected if The installed version is any version before 2.0.4 (e.g., 2.0.3, 2.0.0, 1.x.x).
  3. Identify system architecture
    Check if the machine is 32-bit by running 'uname -m' or 'getconf LONG_BIT'. The vulnerability only affects 32-bit machines.
    Affected if The system architecture is 32-bit (i686, i386, or LONG_BIT returns 32).
  4. Verify CUPS configuration and usage
    Check if CUPS (Common UPdate Server) is configured for the Basics Station. Look for cupsmi.ini, cups.conf, or similar configuration files in the station data directory.
    Affected if CUPS is actively configured and the station communicates with a CUPS server.

You are affected if LoRa Basics Station version is below 2.0.4, running on a 32-bit machine, and CUPS is configured for server updates.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.0.4 or later
Fixed in 2.0.4
Interim mitigation

Upgrade LoRa Basics Station to version 2.0.4 or later. As a workaround, enable TLS authentication on CUPS transactions to prevent attackers from intercepting or tampering with server responses.

Fix this in Lora Basics Station Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-4060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-4060 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data