Skip to content
Noroxi
CVE-2017-6519· NVD / CVE Program· CNA mitre

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, whic

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.

CriticalCVSS 9.1 · v3.1—No exploit Fix available
Published
Apr 30, 2017
Updated
Jun 16, 2026
EPSS
3.2% · 88th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
avahiavahi
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • avahi avahiup to 0.6.32 inclusive
  • avahi avahi0.7
  • canonical ubuntu linux12.04
  • canonical ubuntu linux14.04
  • canonical ubuntu linux16.04
  • canonical ubuntu linux18.04
  • canonical ubuntu linux18.10

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10avahibefore 0.7-r20.7-r2
Alpine:v3.7avahibefore 0.6.32-r50.6.32-r5
Debian:12avahibefore 0.7-50.7-5
openSUSE:Tumbleweedavahibefore 0.8-7.20.8-7.2
Red Hat:enterprise_linux:7::clientavahibefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-autoipdbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-compat-howlbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-compat-howl-develbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-compat-libdns_sdbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-compat-libdns_sd-develbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-debuginfobefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-develbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-dnsconfdbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-glibbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-glib-develbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-gobjectbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-gobject-develbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-libsbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-qt3before 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-qt3-develbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-qt4before 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-qt4-develbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-toolsbefore 0:0.6.31-20.el70:0.6.31-20.el7
Red Hat:enterprise_linux:7::clientavahi-uibefore 0:0.6.31-20.el70:0.6.31-20.el7

+3

Other highest-scoring records for the same primary product.

  • CVE-2008-5081The originates_from_local_legacy_unicast_socket function (avahi-core/server.c) in avahi-daemon in Avahi before 0.6.24 allows remote attacker
    38Monitor
  • CVE-2021-26720avahi-daemon-check-dns.sh in the Debian avahi package through 0.8-4 is executed as root via /etc/network/if-up.d/avahi-daemon, and allows a
    31Monitor
  • CVE-2011-1002avahi-core/socket.c in avahi-daemon in Avahi before 0.6.29 allows remote attackers to cause a denial of service (infinite loop) via an empty
    29Monitor
  • CVE-2026-24401Avahi has Uncontrolled Recursion in lookup_handle_cname function
    26Monitor
  • CVE-2025-68471Avahi has a reachable assertion in lookup_start
    26Monitor
  • CVE-2025-68468Avahi has a reachable assertion in lookup_multicast_callback
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:avahi0.7-r2 · Alpine:v3.10Package registry (OSV)
debian:avahi0.7-5 · Debian:12Package registry (OSV)
opensuse:avahi0.8-7.2 · openSUSE:TumbleweedPackage registry (OSV)
red hat:avahi0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-autoipd0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-compat-howl0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-compat-howl-devel0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-compat-libdns_sd0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-compat-libdns_sd-devel0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-debuginfo0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-devel0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-glib0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-gobject0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-libs0:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:avahi-ui-gtk30:0.6.31-20.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

nvd-secondary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records