Security Advisory

CVE-2023-38473: Avahi Alternative Host Name Assertion

Last updated:
  • CVE-2023-38473

CVE-2023-38473 is a reachable assertion (CWE-617) in Avahi's avahi_alternative_host_name() function. Any local process that can call the GetAlternativeHostName method over D-Bus with a crafted name such as ")." makes avahi-daemon before 0.9 abort, and the device drops out of mDNS discovery. NVD scores it 5.5; commit b448c9f in v0.9-rc1 fixes it.

Vulnerability summary

CVSS base score

5.5

Medium severity

EPSS score (FIRST)

0.3%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2023-38473 · Source: NVD

Affected components

ComponentCPEVersion range
Avahi (avahi-daemon, avahi-common)cpe:2.3:a:avahi:avahi:*:*:*:*:*:*:*:*before 0.9 (NVD); before 0.9-rc1 (Red Hat CNA record); fixed upstream by commit b448c9f, contained in tag v0.9-rc1
Debian avahi packagepkg:deb/debian/avahibullseye fixed in 0.8-5+deb11u3 (DLA-3990-1, 2024-12-09); bookworm fixed in 0.8-10+deb12u1; unstable fixed in 0.8-14; buster postponed (Debian security tracker, as of 2026-11-20)
Buildroot package/avahi (Avahi 0.8)—patched with 0010-common-derive-alternative-host-name-from-its-unescaped-version.patch (commit e728d350, 2026-02-13); first in Buildroot 2026.02, 2025.11.2 and 2025.02.11; earlier releases build Avahi 0.8 without it
Yocto Project poky meta/recipes-connectivity/avahi (Avahi 0.8)—kirkstone and scarthgap carry CVE-2023-38473.patch, a backport of b448c9f (as of 2026-11-20)
OpenWrt packages feed libs/avahi—openwrt-24.10 and openwrt-25.12 build 0.9-rc5 (contains the fix); openwrt-23.05 builds 0.8 with no patch for this CVE (as of 2026-11-20)

What does this mean for affected devices?

CVE-2023-38473 is the last of five reachable assertions in Avahi published together on 2023-11-02 (CVE-2023-38469 to CVE-2023-38473). NVD describes it as "a reachable assertion" in the avahi_alternative_host_name() function and lists Avahi before 0.9 as affected. Red Hat is the CNA (CVE record).

How is CVE-2023-38473 triggered?

The upstream report, Avahi issue 451, reproduces it with one D-Bus call: busctl call org.freedesktop.Avahi / org.freedesktop.Avahi.Server GetAlternativeHostName "s" ').'. The daemon then aborts on the assertion avahi_is_valid_host_name(r) in alternative.c. A second report, issue 487, hits the same assertion with a long name ending in a backslash. In Avahi 0.8 the D-Bus handler passes the caller's string straight to avahi_alternative_host_name(), and the D-Bus policy that Avahi ships allows anyone to call methods on the server except SetHostName. So no special group membership is needed, and unlike CVE-2023-38469, setting disable-user-service-publishing=yes does not close this path, because the method publishes nothing.

The fix is commit b448c9f by Michal Sekletar ("common: derive alternative host name from its unescaped version"), merged on 2023-10-18 and contained in tag v0.9-rc1. It unescapes the label before building the alternative name, so cases such as an unescaped trailing dot can no longer produce an invalid result.

How severe is CVE-2023-38473?

NVD's Primary score is CVSS v3.1 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Red Hat's CNA score is 6.2 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), with no privileges required. NVD and Red Hat both list CWE-617. The impact is availability only: on a printer, camera, NAS or gateway, avahi-daemon stops and the device disappears from service discovery until the daemon restarts. It is not in the CISA KEV catalog as of 2026-11-20 (catalog version 2026.11.18, 1,786 entries), and FIRST EPSS gives it 0.0032, the 25.5th percentile, in the 2026-11-19 dataset.

Which firmware builds carry the fix?

Most embedded builds ship Avahi 0.8 with backports, so the version string alone does not tell you the status.

  • Buildroot builds Avahi 0.8. Commit e728d350 of 2026-02-13 added 0010-common-derive-alternative-host-name-from-its-unescaped-version.patch (upstream b448c9f) together with fixes for the other 2023 assertions and later Avahi CVEs. It shipped in Buildroot 2026.02 and in the 2025.11.2 and 2025.02.11 point releases; images built from older releases carry the unpatched 0.8.
  • Yocto Project: poky kirkstone and scarthgap apply CVE-2023-38473.patch, a backport of b448c9f added in November 2023.
  • OpenWrt: the packages feed builds 0.9-rc5 on openwrt-24.10 and openwrt-25.12; openwrt-23.05 builds 0.8 with no patch for this CVE as of 2026-11-20.
  • Debian fixed bullseye in 0.8-5+deb11u3 with DLA-3990-1, bookworm in 0.8-10+deb12u1 and unstable in 0.8-14; buster was postponed as a minor issue (Debian security tracker).

We found no device vendor or CISA advisory that names products for this CVE as of 2026-11-20.

How do you fix or mitigate CVE-2023-38473?

Rebuild with Avahi 0.9-rc1 or later, or apply b448c9f to 0.8, then confirm that the GetAlternativeHostName call from issue 451 returns an error instead of killing the daemon. Where a rebuild is slow, make sure no untrusted local process (a container, a plugin runtime, a web UI user account) can reach the system D-Bus. Our Avahi and mDNS/DNS-SD vulnerabilities guide covers version matching and hardening; related Avahi flaws on this site include the local CVE-2021-3468, the off-link amplification CVE-2017-6519 and the network-reachable CVE-2026-24401.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD (read 2026-11-20): status Modified; published 2023-11-02T16:15:08.773; reachable assertion in avahi_alternative_host_name(); NVD Primary CVSS v3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H; Red Hat Secondary 6.2 (PR:N); CWE-617 from NVD and Red Hat; CPE avahi:avahi versions before 0.9; references Red Hat bugzilla 2191694 and DLA-3990-1. — NVD
  • CVE record (checked 2026-11-20): state PUBLISHED, CNA Red Hat, published 2023-11-02; CNA CVSS v3.1 6.2; affected avahi from 0 before 0.9-rc1. — CVE.org
  • Avahi issue 451 (read 2026-11-20): busctl GetAlternativeHostName with ').' triggers assertion avahi_is_valid_host_name(r) in alternative.c and SIGABRT; closed 2023-10-18 by commit b448c9f. Issue 487 reports the same assertion with a long name ending in a backslash. Avahi 0.8 dbus-protocol.c passes the string directly to avahi_alternative_host_name(); avahi-dbus.conf allows anyone to call server methods except SetHostName. — Avahi GitHub
  • Commit b448c9f (Michal Sekletar, authored 2023-10-11, committed 2023-10-18), read 2026-11-20: 'common: derive alternative host name from its unescaped version', Fixes #451 #487, CVE-2023-38473; contained in tag v0.9-rc1. — Avahi GitHub
  • Buildroot (read 2026-11-20): AVAHI_VERSION 0.8; patch 0010 (upstream b448c9f) with AVAHI_IGNORE_CVES += CVE-2023-38473, added by commit e728d350 (Thomas Perale, committed 2026-02-13); present in tags 2026.02, 2025.11.2, 2025.02.11, absent in 2025.11.1 and 2025.02.10. — Buildroot
  • Yocto poky (read 2026-11-20): avahi_0.8.bb on kirkstone and scarthgap lists file://CVE-2023-38473.patch, a backport of b448c9f (Meenali Gupta), added 2023-11-28 on kirkstone. — Yocto Project poky
  • OpenWrt packages feed (read 2026-11-20): libs/avahi PKG_VERSION 0.9_rc5 on master, openwrt-25.12 and openwrt-24.10; 0.8 with no CVE-2023-38473 patch on openwrt-23.05. — OpenWrt packages
  • Debian security tracker and DLA-3990-1 (read 2026-11-20): bullseye 0.8-5+deb11u3 (DLA-3990-1, 2024-12-09), bookworm 0.8-10+deb12u1, unstable 0.8-14 (bug 1054880); buster postponed (minor issue); fix commit b448c9f (v0.9-rc1). — Debian
  • Not in the CISA KEV catalog, version 2026.11.18 (1,786 entries), checked 2026-11-20. — CISA KEV
  • EPSS 0.0032, percentile 0.25473, dataset 2026-11-19, read 2026-11-20. — FIRST EPSS

Related advisories

Sources

  1. NVD: CVE-2023-38473
  2. CVE.org record CVE-2023-38473 (CNA: Red Hat)
  3. Red Hat Bugzilla 2191694
  4. Avahi issue 451: reachable assertion in avahi_alternative_host_name
  5. Avahi commit b448c9f (fix)
  6. oss-security: CVEs assigned for reachable assertions in avahi (2023-10-06)
  7. Buildroot commit e728d350: package/avahi: patch various security vulnerabilities
  8. Yocto Project poky (kirkstone): avahi_0.8.bb
  9. OpenWrt packages (openwrt-23.05): libs/avahi/Makefile
  10. Debian security tracker: CVE-2023-38473
  11. Debian LTS Advisory DLA-3990-1: avahi security update
  12. CISA KEV
  13. FIRST EPSS

Frequently asked questions

Which Avahi version fixes CVE-2023-38473?

Upstream commit b448c9f, contained in tag v0.9-rc1; Avahi 0.8, the last stable release, does not include it. Debian, Buildroot and Yocto backport it to Avahi 0.8: Debian in 0.8-5+deb11u3 and 0.8-10+deb12u1, Buildroot as patch 0010, Yocto kirkstone and scarthgap as CVE-2023-38473.patch.

Who can trigger CVE-2023-38473?

A local process that can send messages to avahi-daemon over the system D-Bus. The GetAlternativeHostName method is open to all users under Avahi's shipped D-Bus policy, so Red Hat scores it with no privileges required. It is not reachable from the network, and disable-user-service-publishing does not block it.

Is my Buildroot, Yocto or OpenWrt image affected?

Buildroot images are patched from 2026.02, 2025.11.2 and 2025.02.11; older releases build Avahi 0.8 without the fix. Yocto kirkstone and scarthgap carry the backport. OpenWrt 24.10 and 25.12 build 0.9-rc5, while openwrt-23.05 builds 0.8 without a patch (as of 2026-11-20).

Is CVE-2023-38473 exploited?

It is not in the CISA KEV catalog as of 2026-11-20 (catalog version 2026.11.18, 1,786 entries). FIRST EPSS gives it 0.0032, the 25.5th percentile, in the 2026-11-19 dataset. The impact is a crash of avahi-daemon, not code execution.