USN-5008-1: Avahi vulnerabilities

Publication date

7 July 2021

Overview

Several security issues were fixed in Avahi.


Packages

  • avahi - IPv4LL network address configuration daemon

Details

Thomas Kremer discovered that Avahi incorrectly handled termination signals
on the Unix socket. A local attacker could possibly use this issue to cause
Avahi to hang, resulting in a denial of service. This issue only affected
Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 20.10. (CVE-2021-3468)

It was discovered that Avahi incorrectly handled certain hostnames. A local
attacker could possibly use this issue to cause Avahi to crash, resulting
in a denial of service. This issue only affected Ubuntu 20.10 and Ubuntu
21.04. (CVE-2021-3502)

Thomas Kremer discovered that Avahi incorrectly handled termination signals
on the Unix socket. A local attacker could possibly use this issue to cause
Avahi to hang, resulting in a denial of service. This issue only affected
Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 20.10. (CVE-2021-3468)

It was discovered that Avahi incorrectly handled certain hostnames. A local
attacker could possibly use this issue to cause Avahi to crash, resulting
in a denial of service. This issue only affected Ubuntu 20.10 and Ubuntu
21.04. (CVE-2021-3502)

Update instructions

In general, a standard system update will make all the necessary changes.

Learn more about how to get the fixes.

The problem can be corrected by updating your system to the following package versions:

Ubuntu Release Package Version
21.04 hirsute libavahi-core7 –  0.8-5ubuntu3.1
avahi-daemon –  0.8-5ubuntu3.1
20.10 groovy libavahi-core7 –  0.8-3ubuntu1.1
avahi-daemon –  0.8-3ubuntu1.1
20.04 focal libavahi-core7 –  0.7-4ubuntu7.1
avahi-daemon –  0.7-4ubuntu7.1
18.04 bionic libavahi-core7 –  0.7-3.1ubuntu1.3
avahi-daemon –  0.7-3.1ubuntu1.3

Reduce your security exposure

Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.


Have additional questions?

Talk to a member of the team ›