Skip to content

Product

ubuntu/mosquitto vulnerabilities

29 published CVES affecting ubuntu/mosquitto, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
29
Critical
3
High
17
Medium
9
Low
0
Unscored
0
CISA KEV
0

Latest ubuntu/mosquitto CVEs

Newest publication first · page 1 of 2

  1. CriticalCVSS 9.8 EPSS 1.0%

    In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with protocol websockets mishandles empty WebSocket data frames. net__read_ws() in lib/net_ws.c returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payloa...

  2. CriticalCVSS 9.1 EPSS 0.18%

    In Eclipse Mosquitto versions 2.1.0 to 2.1.2, a broker with a listener that is configured to use the PROXY protocol v2 is vulnerable to an untrusted proxy providing details that cause the broker to accept fake SSL information. This can be mitigated by following the documented req...

  3. MediumCVSS 6.0 EPSS 0.75%

    In Eclipse Mosquito, versions from 2.0.0 through 2.0.18, if a Mosquitto broker is configured to create an outgoing bridge connection, and that bridge connection has an incoming topic configured that makes use of topic remapping, then if the remote connection sends a crafted PUBLI...

  4. HighCVSS 7.2 EPSS 59.2%

    In Eclipse Mosquitto, from version 1.3.2 through 2.0.18, if a malicious broker sends a crafted SUBACK packet with no reason codes, a client using libmosquitto may make out of bounds memory access when acting in its on_subscribe callback. This affects the mosquitto_sub and mosquit...

  5. CVE-2024-8376 Memory leak

    Published
    HighCVSS 7.2 EPSS 0.75%

    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.

  6. HighCVSS 7.5 EPSS 1.3%

    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 se...

  7. MediumCVSS 5.3 EPSS 1.3%

    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.

  8. MediumCVSS 6.5 EPSS 1.1%

    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.

  9. HighCVSS 8.1 EPSS 1.5%

    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, clie...

  10. HighCVSS 8.1 EPSS 1.4%

    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...

  11. MediumCVSS 6.5 EPSS 0.80%

    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 ma...

  12. MediumCVSS 5.3 EPSS 1.4%

    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 s...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.