Vulnerabilities (CVE)

Filtered by vendor Eclipse Subscribe
Filtered by product Mosquitto
Total 26 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2017-7655 2 Debian, Eclipse 2 Debian Linux, Mosquitto 2024-11-21 5.0 MEDIUM 7.5 HIGH
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.
CVE-2017-7654 2 Debian, Eclipse 2 Debian Linux, Mosquitto 2024-11-21 5.0 MEDIUM 7.5 HIGH
In Eclipse Mosquitto 1.4.15 and earlier, a Memory Leak vulnerability was found within the Mosquitto Broker. Unauthenticated clients can send crafted CONNECT packets which could cause a denial of service in the Mosquitto Broker.
CVE-2017-7653 2 Debian, Eclipse 2 Debian Linux, Mosquitto 2024-11-21 3.5 LOW 5.3 MEDIUM
The Eclipse Mosquitto broker up to version 1.4.15 does not reject strings that are not valid UTF-8. A malicious client could cause other clients that do reject invalid UTF-8 strings to disconnect themselves from the broker by sending a topic string which is not valid UTF-8, and so cause a denial of service for the clients.
CVE-2017-7652 2 Debian, Eclipse 2 Debian Linux, Mosquitto 2024-11-21 6.0 MEDIUM 7.5 HIGH
In Eclipse Mosquitto 1.4.14, if a Mosquitto instance is set running with a configuration file, then sending a HUP signal to server triggers the configuration to be reloaded from disk. If there are lots of clients connected so that there are no more file descriptors/sockets available (default limit typically 1024 file descriptors on Linux), then opening the configuration file will fail.
CVE-2017-7651 2 Debian, Eclipse 2 Debian Linux, Mosquitto 2024-11-21 5.0 MEDIUM 7.5 HIGH
In Eclipse Mosquitto 1.4.14, a user can shutdown the Mosquitto server simply by filling the RAM memory with a lot of connections with large payload. This can be done without authentications if occur in connection phase of MQTT protocol.
CVE-2024-8376 1 Eclipse 1 Mosquitto 2024-11-15 N/A 7.5 HIGH
In Eclipse Mosquitto up to version 2.0.18a, an attacker can achieve memory leaking, segmentation fault or heap-use-after-free by sending specific sequences of "CONNECT", "DISCONNECT", "SUBSCRIBE", "UNSUBSCRIBE" and "PUBLISH" packets.