VulnerabilityPublished 21 Mar 2024Updated 5 Nov 2024

CVE-2024-29862: chirpstack-mqtt-forwarder

Affects chirpstack-mqtt-forwarderSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.2.1 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.2.1, 4.0.11

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade chirpstack/chirpstack-mqtt-forwarder to 4.2.1; chirpstack/chirpstack-gateway-bridge to 4.0.11.

Affected software

Product	Affected	Fixed in
GitHubchirpstack/chirpstack-mqtt-forwarder`pkg:github/chirpstack/chirpstack-mqtt-forwarder`Other threats	Affected <4.2.1	Fixed in 4.2.1
GitHubchirpstack/chirpstack-gateway-bridge`pkg:github/chirpstack/chirpstack-gateway-bridge`Other threats	Affected <4.0.11	Fixed in 4.0.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, network operators should implement additional perimeter firewall rules to restrict unsolicited inbound TCP traffic to ChirpStack components, especially from untrusted networks. Deploying network intrusion detection systems (NIDS) to monitor for anomalous TCP packets that do not conform to expected connection states can help detect exploitation attempts. Segmentation of IoT networks and limiting exposure of ChirpStack services to the internet reduces attack surface. Regularly auditing firewall configurations and ensuring stateful inspection is correctly enforced can mitigate risk. Finally, monitoring vendor advisories and subscribing to security mailing lists will ensure timely awareness of patch releases and exploit reports.

Description

The Kerlink firewall in ChirpStack chirpstack-mqtt-forwarder before 4.2.1 and chirpstack-gateway-bridge before 4.0.11 wrongly accepts certain TCP packets when a connection is not in the ESTABLISHED state.

Impact

The vulnerability can lead to unauthorized disclosure of sensitive information by allowing attackers to bypass firewall protections and send unsolicited TCP packets to ChirpStack components. This can compromise the confidentiality of data transmitted within IoT networks, potentially exposing device telemetry, network configurations, or user data. Since ChirpStack is used to manage LoRaWAN gateways and devices, attackers could leverage this flaw to gather intelligence on network topology or intercept communications. Although the vulnerability does not affect data integrity or system availability directly, the confidentiality breach could facilitate further attacks or unauthorized access. Organizations deploying ChirpStack in critical infrastructure, smart city applications, or industrial IoT environments face increased risk of data leakage and espionage. The ease of exploitation without authentication or user interaction increases the likelihood of automated scanning and exploitation attempts once public exploits emerge.

References

Community reviews

Loading reviews…