2019-06-18 - Eduardo Barretto <firstname.lastname@example.org>
mosquitto (1.4.8-1ubuntu0.16.04.7) xenial-security; urgency=medium
* SECURITY UPDATE: DoS (client disconnect) via invalid UTF-8 strings
- debian/patches/add-validate-utf8.patch: Add validate UTF-8
- debian/patches/CVE-2017-7653.patch: Add UTF-8 tests, plus some validation
* SECURITY UPDATE: Memory leak in the Mosquitto Broker allows unauthenticated
clients to send crafted CONNECT packets which could cause DoS
- debian/patches/CVE-2017-7654.patch: Fix memory leak that could be caused
by a malicious CONNECT packet
2019-02-13 - Roger A. Light <email@example.com>
mosquitto (1.4.8-1ubuntu0.16.04.6) xenial-security; urgency=medium
* Fix regression in update for CVE-2018-12546.
2019-02-06 - Roger A. Light <firstname.lastname@example.org>
mosquitto (1.4.8-1ubuntu0.16.04.5) xenial-security; urgency=medium
* SECURITY UPDATE: If Mosquitto 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.
- debian/patches/mosquitto-1.4.x-cve-2018-12551.patch: this fix introduces
more stringent parsing tests on the password file data.
* SECURITY UPDATE: If an ACL file is empty, or has only blank lines or
comments, then mosquitto treats the ACL file as not being defined, which
means that no topic access is denied. Although denying access to all
topics is not a useful configuration, this behaviour is unexpected and
could lead to access being incorrectly granted in some circumstances.
- debian/patches/mosquitto-1.4.x-cve-2018-12550.patch: this fix ensures
that if an ACL file is defined but no rules are defined, then access will
* SECURITY UPDATE: If a client publishes a retained message to a topic that
they have access to, and then their access to that topic is revoked, the
retained message will still be delivered to future subscribers. This
behaviour may be undesirable in some applications, so a configuration
option `check_retain_source` has been introduced to enforce checking of
the retained message source on publish.
- debian/patches/mosquitto-1.4.8-cve-2018-12546.patch: this patch stores
the originator of the retained message, so security checking can be
carried out before re-publishing. The complexity of the patch is due to
the need to save this information across broker restarts.
2018-09-05 - Eduardo Barretto <email@example.com>
mosquitto (1.4.8-1ubuntu0.16.04.4) xenial-security; urgency=medium
* SECURITY UPDATE: in case all sockets/file descriptors are exhausted,
then opening the configuration file will fail.
- debian/patches/mosquitto-1.4.x_cve-2017-7652.patch: this is a fix
to avoid default config values after reloading configuration by
2018-03-01 - Emmet Hikory <firstname.lastname@example.org>
mosquitto (1.4.8-1ubuntu0.16.04.3) xenial-security; urgency=medium
* SECURITY UPDATE: upstream patch for CVE 2017-7651 (LP: #1752591)
2017-06-26 - Roger A. Light <email@example.com>
mosquitto (1.4.8-1ubuntu0.16.04.2) xenial-security; urgency=low
* SECURITY UPDATE: Persistence file is world readable, which may expose
sensitive data (LP: #1700490).
- debian/patches/mosquitto-1.4.x_cve-2017-9868.patch: Set umask to
restrict persistence file read access to owner.