CVE-2023-38472 is a reachable assertion (CWE-617) in Avahi's avahi_rdata_parse() function. A local process that publishes a record with empty data through avahi-daemon's D-Bus entry group interface makes the daemon abort, unless disable-user-service-publishing is set to yes. NVD scores it 5.5; commit b024ae5 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-38472 · Source: NVD
Affected components
| Component | CPE | Version 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 (commit b024ae5); backported in Buildroot 0.8 patch 0009, Yocto kirkstone/scarthgap CVE-2023-38472.patch, Debian 0.8-5+deb11u3 and 0.8-10+deb12u1 |
What does this mean for affected devices?
CVE-2023-38472 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 avahi_rdata_parse() 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-38472 triggered?
The upstream report, Avahi issue 452, shows a client that creates an entry group and adds a raw record with empty record data, for example avahi_entry_group_add_record() with a zero-length rdata, which becomes the D-Bus call org.freedesktop.Avahi.EntryGroup AddRecord. The daemon passes the empty buffer to avahi_rdata_parse() and aborts on the assertion rdata (dns.c). The report states that it "can be triggered by unprivileged users unless disable-user-service-publishing is set to yes explicitly. By default it's set to no." The oss-security post that announced the five CVEs repeats this.
How severe is CVE-2023-38472?
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.0032, the 25.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
0009-core-make-sure-there-is-rdata-to-process-before-parsing-it.patch(upstream b024ae5) together with fixes for the other 2023 assertions and later Avahi CVEs, and lists CVE-2023-38472 inAVAHI_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-38472.patch(b024ae5) 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-38472?
The fix is commit b024ae5 by Michal Sekletar ("core: make sure there is rdata to process before parsing it"), merged on 2023-10-20 and contained in tag v0.9-rc1. Rebuild with Avahi 0.9-rc1 or later, or apply b024ae5 to 0.8.
Where a rebuild is slow, set disable-user-service-publishing=yes in avahi-daemon.conf. Most devices publish their services from avahi-daemon's own service files and never need local applications to publish over D-Bus, so the setting closes this path without losing features. The same setting also covers CVE-2023-38469, but not the lookup and rename assertions CVE-2023-38470 and CVE-2023-38471.
Our Avahi and mDNS/DNS-SD vulnerabilities guide covers the full hardening configuration, and the off-link amplification CVE-2017-6519 is the network-side Avahi issue to check in the same review.
Evidence
- Reachable assertion in avahi_rdata_parse(); 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 avahi_rdata_parse'; avahi affected from 0 before 0.9-rc1; CNA CVSS 3.1 6.2; checked 2026-11-21. — CVE.org
- EntryGroup AddRecord with empty rdata triggers 'dns.c:861: avahi_rdata_parse: Assertion rdata failed' from avahi_dbus_msg_entry_group_impl; 'can be triggered by unprivileged users unless disable-user-service-publishing is set to yes explicitly. By default it's set to no.'; closed 2023-10-20. — Avahi issue 452
- 'core: make sure there is rdata to process before parsing it' (Michal Sekletar, committed 2023-10-20); in v0.9-rc1, not in v0.8 (GitHub compare). — Avahi commit b024ae5
- Alan Coopersmith, 2023-10-06: CVE-2023-38472 is issue 452, quoting the disable-user-service-publishing condition. — oss-security
- Buildroot e728d350 (2026-02-13) adds patch 0009 (b024ae5, CVE: CVE-2023-38472), AVAHI_IGNORE_CVES += CVE-2023-38472; in tag 2026.02. Yocto kirkstone and scarthgap list CVE-2023-38472.patch (b024ae5). 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 b024ae5 (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.0032, percentile 0.25603, dataset 2026-11-20, read 2026-11-21. — FIRST EPSS

Related advisories
Sources
- NVD: CVE-2023-38472
- CVE.org record CVE-2023-38472 (CNA: Red Hat)
- Red Hat Bugzilla 2191692
- Avahi issue 452: reachable assertion in avahi_rdata_parse
- Avahi commit b024ae5 (fix)
- oss-security: CVEs assigned for reachable assertions in avahi (2023-10-06)
- Buildroot commit e728d350: package/avahi: patch various security vulnerabilities
- Yocto Project poky (kirkstone): avahi_0.8.bb
- OpenWrt packages (openwrt-23.05): libs/avahi/Makefile
- Debian security tracker: CVE-2023-38472
- Debian LTS Advisory DLA-3990-1: avahi security update
- CISA KEV
- FIRST EPSS
Frequently asked questions
Who can trigger CVE-2023-38472?
A local user or process that can create an entry group over avahi-daemon's D-Bus interface and add a raw record. Unprivileged users can do this unless disable-user-service-publishing is set to yes; the default is no. It is not reachable from the network (per Avahi issue 452).
What is the quickest mitigation on a device?
Set disable-user-service-publishing=yes in avahi-daemon.conf if no local application needs to publish records over D-Bus. Services defined in avahi-daemon's own service files keep working (per Avahi issue 452 and the oss-security announcement).
Which fix should a Buildroot or Yocto image carry?
Upstream commit b024ae5, part of v0.9-rc1. Buildroot ships it as patch 0009 on Avahi 0.8 since commit e728d350 (in 2026.02); Yocto kirkstone and scarthgap ship it as CVE-2023-38472.patch (per the Buildroot and Yocto recipes).
Is CVE-2023-38472 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.0032, the 25.6th percentile, in the 2026-11-20 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?