Security Advisory

CVE-2023-38471: Avahi SetHostName D-Bus Assertion

Last updated:
  • CVE-2023-38471

CVE-2023-38471 is a reachable assertion (CWE-617) in Avahi's D-Bus SetHostName handler. A local process that asks avahi-daemon to change the host name to a value such as 'A\.B' makes the daemon abort, and on Avahi 0.8 the Server2 interface lets unprivileged users make that call. NVD scores it 5.5; 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-38471 · Source: NVD

Affected components

ComponentCPEVersion range
Avahi (avahi-daemon)cpe:2.3:a:avahi:avahi:*:*:*:*:*:*:*:*before 0.9 (NVD CPE); before 0.9-rc1 (CNA). Fixed upstream in v0.9-rc1 (commits 894f085 and b675f70); backported in Buildroot 0.8 patches 0007/0008, Yocto kirkstone/scarthgap CVE-2023-38471-1/-2, Debian 0.8-5+deb11u3 and 0.8-10+deb12u1

What does this mean for affected devices?

CVE-2023-38471 is one 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 dbus_set_host_name function and lists Avahi before 0.9 as affected, plus Red Hat Enterprise Linux 8 and 9. Red Hat is the CNA (CVE record) and gives the affected range as versions before 0.9-rc1.

How is CVE-2023-38471 triggered?

The upstream report, Avahi issue 453, reproduces it with one D-Bus call that asks the daemon to change the host name: busctl call org.freedesktop.Avahi / org.freedesktop.Avahi.Server2 SetHostName "s" 'A\.B'. The escaped dot reaches avahi_server_set_host_name(), and the daemon aborts on the assertion r in avahi_domain_equal() (domain.c).

Who can make that call matters on a device. The D-Bus policy shipped with Avahi 0.8 lets anyone call methods on the daemon except SetHostName on the org.freedesktop.Avahi.Server interface, which is kept for root and the privileged access group. Avahi 0.8 also answers the same method on the newer org.freedesktop.Avahi.Server2 interface, and the policy had no deny rule for it. The issue reporter therefore notes that unprivileged local users can trigger the crash unless commit 1c599d8 ("dbus: deny SetHostName via org.freedesktop.Avahi.Server2 as well", 2022-12-09) is backported. Setting disable-user-service-publishing=yes does not help here.

How severe is CVE-2023-38471?

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 (CVSS:3.1/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 (reachable assertion). The impact is availability only: avahi-daemon stops and the device disappears from mDNS/DNS-SD discovery until the daemon restarts. It is not in the CISA KEV catalog as of 2026-11-21 (catalog version 2026.11.20, 1,790 entries), and FIRST EPSS gives it 0.00328, the 26.6th percentile, in the 2026-11-20 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 0007-core-extract-host-name-using-avahi-unescape-label.patch (upstream 894f085) and 0008-core-return-errors-from-avahi-server-set-host-name-properly.patch (upstream b675f70) together with fixes for the other 2023 assertions and later Avahi CVEs, and lists CVE-2023-38471 in AVAHI_IGNORE_CVES. Buildroot 2026.02 contains the commit; images built from a tree without it carry the unpatched 0.8.
  • Yocto Project: poky kirkstone and scarthgap apply CVE-2023-38471-1.patch (a backport of 894f085) and CVE-2023-38471-2.patch (b675f70) to Avahi 0.8.
  • OpenWrt: the packages feed builds 0.9-rc5 on openwrt-24.10 and openwrt-25.12; openwrt-23.05 builds 0.8 (release 8) with no patch for this CVE as of 2026-11-21.
  • Debian fixed bullseye in 0.8-5+deb11u3 with DLA-3990-1, bookworm in 0.8-10+deb12u1, trixie in 0.8-16 and unstable in 0.8-18; 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-21.

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

The fix is commit 894f085 by Michal Sekletar ("core: extract host name using avahi_unescape_label()"), merged on 2023-10-24, with the follow-up commit b675f70 ("core: return errors from avahi_server_set_host_name properly") of the same day; both are in tag v0.9-rc1. Rebuild with Avahi 0.9-rc1 or later, or apply both commits to 0.8, then confirm that the SetHostName call from issue 453 returns an error instead of killing the daemon.

Independently of the code fix, check the installed avahi-dbus.conf: if it denies SetHostName only on the Server interface, add the Server2 deny rule from commit 1c599d8, so that only root and the privileged group can rename the device at all. Keep untrusted local processes (containers, plugin runtimes, web UI accounts) away from the system D-Bus.

Our Avahi and mDNS/DNS-SD vulnerabilities guide covers version matching and hardening. The sibling assertions CVE-2023-38470 and CVE-2023-38472 need the same patch-list check, and the local infinite loop CVE-2021-3468 is fixed by the same Buildroot commit.

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

  • Reachable assertion in dbus_set_host_name; NVD Primary CVSS v3.1 5.5 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; CPE avahi before 0.9, RHEL 8.0 and 9.0; published 2023-11-02; read 2026-11-21. — NVD
  • State PUBLISHED; CNA Red Hat; title 'Reachable assertion in dbus_set_host_name'; avahi affected from 0 before 0.9-rc1; CNA CVSS 3.1 6.2; checked 2026-11-21. — CVE.org
  • busctl call ... org.freedesktop.Avahi.Server2 SetHostName 's' 'A\.B' triggers 'domain.c:242: avahi_domain_equal: Assertion r failed' via avahi_server_set_host_name and dbus_set_host_name; 'can be triggered by unprivileged local users unless 1c599d8 is backported'; closed 2023-10-24. — Avahi issue 453
  • v0.8 avahi-dbus.conf.in default policy allows all methods and denies only SetHostName on org.freedesktop.Avahi.Server; v0.8 dbus-protocol.c dispatches common methods (including SetHostName) on Server2; 1c599d8 (2022-12-09) adds the deny rule for Server2 ('the policy wasn't updated when the Server2 interface was introduced'); not in v0.8. — Avahi source v0.8 and commit 1c599d8
  • 894f085 'core: extract host name using avahi_unescape_label()' (Michal Sekletar, committed 2023-10-24) and b675f70 'core: return errors from avahi_server_set_host_name properly' (committed 2023-10-24); both in v0.9-rc1, not in v0.8 (GitHub compare). — Avahi commits
  • Buildroot e728d350 (2026-02-13) adds patches 0007 (894f085) and 0008 (b675f70), both tagged CVE-2023-38471, AVAHI_IGNORE_CVES += CVE-2023-38471; in tag 2026.02. Yocto kirkstone and scarthgap list CVE-2023-38471-1.patch (backport of 894f085) and CVE-2023-38471-2.patch (b675f70). OpenWrt openwrt-23.05 avahi 0.8 release 8 has no patch for it; 24.10 and 25.12 build 0.9_rc5; read 2026-11-21. — Buildroot / Yocto / OpenWrt
  • bullseye fixed 0.8-5+deb11u3 (DLA-3990-1), bookworm 0.8-10+deb12u1, trixie 0.8-16, forky/sid 0.8-18; buster postponed (minor issue); fix 894f085 (v0.9-rc1); read 2026-11-21. — Debian security tracker
  • Not in the CISA KEV catalog version 2026.11.20 (1,790 entries), checked 2026-11-21. — CISA KEV
  • EPSS 0.00328, percentile 0.26569, dataset 2026-11-20, read 2026-11-21. — FIRST EPSS

Related advisories

Sources

  1. NVD: CVE-2023-38471
  2. CVE.org record CVE-2023-38471 (CNA: Red Hat)
  3. Red Hat Bugzilla 2191691
  4. Avahi issue 453: reachable assertion in dbus_set_host_name
  5. Avahi commit 894f085 (fix)
  6. Avahi commit b675f70 (follow-up fix)
  7. Avahi commit 1c599d8: deny SetHostName via org.freedesktop.Avahi.Server2
  8. oss-security: CVEs assigned for reachable assertions in avahi (2023-10-06)
  9. Buildroot commit e728d350: package/avahi: patch various security vulnerabilities
  10. Yocto Project poky (kirkstone): avahi_0.8.bb
  11. OpenWrt packages (openwrt-23.05): libs/avahi/Makefile
  12. Debian security tracker: CVE-2023-38471
  13. Debian LTS Advisory DLA-3990-1: avahi security update
  14. CISA KEV
  15. FIRST EPSS

Frequently asked questions

Can an unprivileged user trigger CVE-2023-38471?

On Avahi 0.8 with the stock D-Bus policy, yes: the policy denies SetHostName only on the Server interface, while the daemon also accepts it on Server2. Upstream commit 1c599d8 adds the missing deny rule. It is not reachable from the network (per Avahi issue 453 and the Avahi source).

Which fix should a Buildroot or Yocto image carry?

Upstream commits 894f085 and b675f70, both in v0.9-rc1. Buildroot ships them as patches 0007 and 0008 on Avahi 0.8 since commit e728d350 (in 2026.02); Yocto kirkstone and scarthgap ship them as CVE-2023-38471-1.patch and CVE-2023-38471-2.patch (per the Buildroot and Yocto recipes).

How severe is CVE-2023-38471?

NVD scores it CVSS v3.1 5.5 (medium): local, availability impact only. Red Hat as CNA scores 6.2 because it rates no privileges required. The worst case is avahi-daemon stopping and the device dropping out of discovery until a restart (per NVD and CVE.org).

Is CVE-2023-38471 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-21 (catalog version 2026.11.20), and FIRST EPSS gives it 0.00328, the 26.6th percentile, in the 2026-11-20 dataset (per CISA KEV and FIRST EPSS).