First published: Fri Feb 24 2017(Updated: )
avahi-daemon in Avahi through 0.6.32 and 0.7 inadvertently responds to IPv6 unicast queries with source addresses that are not on-link, which allows remote attackers to cause a denial of service (traffic amplification) and may cause information leakage by obtaining potentially sensitive information from the responding device via port-5353 UDP packets. NOTE: this may overlap CVE-2015-2809.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/avahi | <=0.7-4+deb10u1<=0.7-4+deb10u3 | 0.8-5+deb11u2 0.8-10 0.8-13 |
ubuntu/avahi | <0.7-3.1ubuntu1.2 | 0.7-3.1ubuntu1.2 |
ubuntu/avahi | <0.7-4ubuntu2.1 | 0.7-4ubuntu2.1 |
ubuntu/avahi | <0.6.31-4ubuntu1.3 | 0.6.31-4ubuntu1.3 |
ubuntu/avahi | <0.6.32~ | 0.6.32~ |
ubuntu/avahi | <0.8 | 0.8 |
Avahi Utilities | <=0.6.32 | |
Avahi Utilities | =0.7 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =16.04 | |
Ubuntu | =18.04 | |
Ubuntu | =18.10 |
Block udp port 5353 at perimeter firewall
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-6519 is rated as a denial of service vulnerability that can lead to traffic amplification.
To fix CVE-2017-6519, upgrade the Avahi package to version 0.8 or later.
Avahi versions up to and including 0.6.32 and 0.7 are affected by CVE-2017-6519.
Yes, CVE-2017-6519 may allow remote attackers to obtain potentially sensitive information.
A workaround for CVE-2017-6519 is to restrict access to the Avahi service to only trusted networks.