Mosquitto Eclipse Mosquitto

Do you want an email whenever new security vulnerabilities are reported in Eclipse Mosquitto?

By the Year

In 2024 there have been 0 vulnerabilities in Eclipse Mosquitto . Last year Mosquitto had 4 security vulnerabilities published. Right now, Mosquitto is on track to have less security vulnerabilities in 2024 than it did last year.

Year Vulnerabilities Average Score
2024 0 0.00
2023 4 6.95
2022 0 0.00
2021 5 6.66
2020 0 0.00
2019 6 7.02
2018 2 7.50

It may take a day or so for new Mosquitto vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Eclipse Mosquitto Security Vulnerabilities

In Eclipse Mosquito before and including 2.0.5, establishing a connection to the mosquitto server without sending data causes the EPOLLOUT event to be added

CVE-2023-5632 7.5 - High - October 18, 2023

In Eclipse Mosquito before and including 2.0.5, establishing a connection to the mosquitto server without sending data causes the EPOLLOUT event to be added, which results excessive CPU consumption. This could be used by a malicious actor to perform denial of service type attack. This issue is fixed in 2.0.6

Excessive Iteration

In Mosquitto before 2.0.16, a memory leak occurs when clients send v5 CONNECT packets with a will message

CVE-2023-3592 7.5 - High - October 02, 2023

In Mosquitto before 2.0.16, a memory leak occurs when clients send v5 CONNECT packets with a will message that contains invalid property types.

Memory Leak

In Mosquitto before 2.0.16, excessive memory is allocated based on malicious initial packets

CVE-2023-0809 5.3 - Medium - October 02, 2023

In Mosquitto before 2.0.16, excessive memory is allocated based on malicious initial packets that are not CONNECT packets.

Allocation of Resources Without Limits or Throttling

The broker in Eclipse Mosquitto 1.3.2 through 2.x before 2.0.16 has a memory leak

CVE-2023-28366 7.5 - High - September 01, 2023

The broker in Eclipse Mosquitto 1.3.2 through 2.x before 2.0.16 has a memory leak that can be abused remotely when a client sends many QoS 2 messages with duplicate message IDs, and fails to respond to PUBREC commands. This occurs because of mishandling of EAGAIN from the libc send function.

Memory Leak

In versions 1.6 to 2.0.11 of Eclipse Mosquitto

CVE-2021-41039 7.5 - High - December 01, 2021

In versions 1.6 to 2.0.11 of Eclipse Mosquitto, an MQTT v5 client connecting with a large number of user-property properties could cause excessive CPU usage, leading to a loss of performance and possible denial of service.

In Eclipse Mosquitto versions 2.0 to 2.0.11, when using the dynamic security plugin, if the ability for a client to make subscriptions on a topic is revoked when a durable client is offline, then existing subscriptions for

CVE-2021-34434 5.3 - Medium - August 30, 2021

In Eclipse Mosquitto versions 2.0 to 2.0.11, when using the dynamic security plugin, if the ability for a client to make subscriptions on a topic is revoked when a durable client is offline, then existing subscriptions for that client are not revoked.

AuthZ

In Eclipse Mosquitto versions 2.07 and earlier

CVE-2021-34432 7.5 - High - July 27, 2021

In Eclipse Mosquitto versions 2.07 and earlier, the server will crash if the client tries to send a PUBLISH packet with topic length = 0.

In Eclipse Mosquitto version 1.6 to 2.0.10, if an authenticated client

CVE-2021-34431 6.5 - Medium - July 22, 2021

In Eclipse Mosquitto version 1.6 to 2.0.10, if an authenticated client that had connected with MQTT v5 sent a crafted CONNECT message to the broker a memory leak would occur, which could be used to provide a DoS attack against the broker.

Memory Leak

In Eclipse Mosquitto version 2.0.0 to 2.0.9, if an authenticated client

CVE-2021-28166 6.5 - Medium - April 07, 2021

In Eclipse Mosquitto version 2.0.0 to 2.0.9, if an authenticated client that had connected with MQTT v5 sent a crafted CONNACK message to the broker, a NULL pointer dereference would occur.

NULL Pointer Dereference

In Eclipse Mosquitto 1.5.0 to 1.6.5 inclusive, if a malicious MQTT client sends a SUBSCRIBE packet containing a topic

CVE-2019-11779 6.5 - Medium - September 19, 2019

In Eclipse Mosquitto 1.5.0 to 1.6.5 inclusive, if a malicious MQTT client sends a SUBSCRIBE packet containing a topic that consists of approximately 65400 or more '/' characters, i.e. the topic hierarchy separator, then a stack overflow will occur.

Stack Exhaustion

If an MQTT v5 client connects to Eclipse Mosquitto versions 1.6.0 to 1.6.4 inclusive, sets a last will and testament, sets a will delay interval, sets a session expiry interval, and the will delay interval is set longer than the session expiry interval, then a use after free error occurs

CVE-2019-11778 5.4 - Medium - September 18, 2019

If an MQTT v5 client connects to Eclipse Mosquitto versions 1.6.0 to 1.6.4 inclusive, sets a last will and testament, sets a will delay interval, sets a session expiry interval, and the will delay interval is set longer than the session expiry interval, then a use after free error occurs, which has the potential to cause a crash in some situations.

Dangling pointer

In Eclipse Mosquitto version

CVE-2017-7655 7.5 - High - March 27, 2019

In Eclipse Mosquitto version from 1.0 to 1.4.15, a Null Dereference vulnerability was found in the Mosquitto library which could lead to crashes for those applications using the library.

NULL Pointer Dereference

When Eclipse Mosquitto version 1.0 to 1.5.5 (inclusive) is configured to use a password file for authentication

CVE-2018-12551 8.1 - High - March 27, 2019

When Eclipse Mosquitto version 1.0 to 1.5.5 (inclusive) is configured to use a password file for authentication, any malformed data in the password file will be treated as valid. This typically means that the malformed data becomes a username and no password. If this occurs, clients can circumvent authentication and get access to the broker by using the malformed username. In particular, a blank line will be treated as a valid empty username. Other security measures are unaffected. Users who have only used the mosquitto_passwd utility to create and modify their password files are unaffected by this vulnerability.

authentification

When Eclipse Mosquitto version 1.0 to 1.5.5 (inclusive) is configured to use an ACL file, and

CVE-2018-12550 8.1 - High - March 27, 2019

When Eclipse Mosquitto version 1.0 to 1.5.5 (inclusive) is configured to use an ACL file, and that ACL file is empty, or contains only comments or blank lines, then Mosquitto will treat this as though no ACL file has been defined and use a default allow policy. The new behaviour is to have an empty ACL file mean that all access is denied, which is not a useful configuration but is not unexpected.

In Eclipse Mosquitto version 1.0 to 1.5.5 (inclusive) when a client publishes a retained message to a topic, then has its access to

CVE-2018-12546 6.5 - Medium - March 27, 2019

In Eclipse Mosquitto version 1.0 to 1.5.5 (inclusive) when a client publishes a retained message to a topic, then has its access to that topic revoked, the retained message will still be published to clients that subscribe to that topic in the future. In some applications this may result in clients being able cause effects that would otherwise not be allowed.

Incorrect Permission Assignment for Critical Resource

Eclipse Mosquitto 1.5.x before 1.5.5

CVE-2018-20145 7.5 - High - December 13, 2018

Eclipse Mosquitto 1.5.x before 1.5.5 allows ACL bypass: if the option per_listener_settings was set to true, and the default listener was in use, and the default listener specified an acl_file, then the acl file was being ignored.

Incorrect Permission Assignment for Critical Resource

In Eclipse Mosquitto versions 1.5 to 1.5.2 inclusive, if a message is published to Mosquitto

CVE-2018-12543 7.5 - High - November 15, 2018

In Eclipse Mosquitto versions 1.5 to 1.5.2 inclusive, if a message is published to Mosquitto that has a topic starting with $, but that is not $SYS, e.g. $test/test, then an assert is triggered that should otherwise not be reachable and Mosquitto will exit.

Improper Input Validation

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Eclipse Mosquitto or by Eclipse? Click the Watch button to subscribe.

Eclipse
Vendor

subscribe