LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28349: An inaccurate frame deduplication process in ChirpStack Network Server 3.9.0 allows a malicious gateway to...

An inaccurate frame deduplication process in ChirpStack Network Server 3.9.0 allows a malicious gateway to perform uplink Denial of Service via malformed frequency attributes in CollectAndCallOnceCollect in internal/uplink/collect.go. NOTE: the vendor's position is that there are no "guarantees that allowing untrusted LoRa gateways to the network should still result in a secure network.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-28349 is a denial-of-service issue in ChirpStack Network Server 3.9.0. A malicious LoRa gateway can disrupt uplink processing by sending malformed frequency attributes. Business urgency depends on whether the organization allows untrusted or weakly controlled gateways into its LoRaWAN network.

Executive priority

Prioritize this for LoRaWAN environments using ChirpStack 3.9.0, especially where third-party or field-managed gateways connect. It is not supported as an internet-wide emergency by the provided sources, but it can affect IoT telemetry availability if gateway trust controls are weak.

Technical view

The CVE describes inaccurate frame deduplication in CollectAndCallOnceCollect within internal/uplink/collect.go. Malformed frequency attributes from a malicious gateway can trigger uplink denial of service. The source bundle names ChirpStack Network Server 3.9.0, but does not provide CVSS, CWE, CPE, or a named fixed release.

Likely exposure

Exposure is most likely in LoRaWAN deployments running ChirpStack Network Server 3.9.0 where gateway identity, onboarding, or network access is not tightly controlled. Environments with only trusted, authenticated gateways have lower practical exposure, consistent with the vendor position in the CVE description.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. The issue requires a malicious gateway in the network trust boundary. Public references include upstream commits and related LoRaWAN security research, but the provided evidence does not establish exploitation in the wild.

Researcher notes

Key evidence gaps are missing CVSS, CWE, CPE, fixed version, and exploit telemetry. Treat the vendor note as important threat-model context: ChirpStack does not guarantee security when untrusted LoRa gateways are allowed into the network.

Mitigation direction

  • Inventory ChirpStack Network Server versions and identify any 3.9.0 deployments.
  • Review upstream commits and vendor guidance for supported upgrade or backport direction.
  • Restrict gateway onboarding to trusted, authenticated devices only.
  • Segment gateway connectivity from critical application and management services.
  • Monitor uplink processing errors and abnormal gateway metadata patterns.

Validation and detection

  • Confirm whether production runs ChirpStack Network Server 3.9.0.
  • Verify gateway authentication, registration, and removal processes.
  • Check whether deployed code includes the referenced upstream changes.
  • Review logs for repeated uplink failures tied to gateway metadata.
  • Validate monitoring detects uplink denial-of-service symptoms.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-28349 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.