p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de mosquitto

Vulnérabilité publiée pour mosquitto au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 25

  1. CVE-2024-3935

    Moyenne · CVSS 6EPSS 0,75%Correctif disponible

    Eclipse Mosquito: Double free vulnerability

    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 PUBLISH packet to the broker a double free will occur with a subsequent crash of the broker.

    • Mettez à jour vers 2.0.20-1
    Publication Mise à jour
  2. CVE-2024-10525

    Élevée · CVSS 7.2EPSS 59,22%Correctif disponible

    Eclipse Mosquito: Heap Buffer Overflow in my_subscribe_callback

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

    • Mettez à jour vers 2.0.20-1
    Publication Mise à jour
  3. CVE-2023-5632

    Élevée · CVSS 7.5EPSS 0,8%Correctif disponible

    Unconditionally adding an event to the epoll causes excessive CPU consumption

    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

    • Mettez à jour vers 2.0.7-1
    Publication Mise à jour
  4. CVE-2023-28366

    Élevée · CVSS 7.5EPSS 1,31%Correctif disponible

    CVE-2023-28366

    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.

    • Mettez à jour vers 2.0.17-1
    Publication Mise à jour
  5. CVE-2021-34431

    Moyenne · CVSS 6.5EPSS 1,11%Correctif disponible

    CVE-2021-34431

    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.

    • Mettez à jour vers 2.0.11-1
    Publication Mise à jour
  6. CVE-2019-11778

    Moyenne · CVSS 5.4EPSS 0,76%Correctif disponible

    CVE-2019-11778

    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.

    • Mettez à jour vers 1.6.6-1
    Publication Mise à jour
  7. CVE-2018-12551

    Élevée · CVSS 8.1EPSS 1,47%Correctif disponible

    CVE-2018-12551

    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.

    • Mettez à jour vers 1.5.6-1
    Publication Mise à jour
  8. CVE-2018-12550

    Élevée · CVSS 8.1EPSS 1,35%Correctif disponible

    CVE-2018-12550

    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.

    • Mettez à jour vers 1.5.6-1
    Publication Mise à jour
  9. CVE-2018-12546

    Moyenne · CVSS 6.5EPSS 0,8%Correctif disponible

    CVE-2018-12546

    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.

    • Mettez à jour vers 1.5.6-1
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →