Security Resilience

CVE-2023-38470

Avahi ≤ 0.9

Published
02 November 2023
Modified
28 October 2026
CVSS Score v3.1 6.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0032 25th percentile
Risk Priority 47 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-38470 is a medium-severity Reachable Assertion (CWE-617) vulnerability in Avahi. Its CVSS base score is 6.2 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

A vulnerability was found in Avahi. A reachable assertion exists in the avahi_escape_label() function.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
T1685 Disable or Modify Tools Defense Impairment
Adversaries may disable, degrade, or tamper with security tools or applications (e.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-38473Same product: Avahi Avahi
CVE-2023-38472Same product: Avahi Avahi
CVE-2023-38469Same product: Avahi Avahi
CVE-2023-38471Same product: Avahi Avahi
CVE-2025-68276Same product: Avahi Avahi
CVE-2025-68468Same product: Avahi Avahi
CVE-2025-68471Same product: Avahi Avahi
CVE-2026-34933Same product: Avahi Avahi
CVE-2023-5871Shared CWE-617
CVE-2024-3567Shared CWE-617

Affected Assets

avahi
avahi
≤ 0.9
redhat
enterprise linux
8.0, 9.0

Mitigating Controls

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent unsafe assertions from being coded in reachable paths.

DE.CM-09 partial match
blocks

Runtime monitoring of software can detect assertion-triggered crashes as adverse events.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover and record reachable-assertion flaws before deployment.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development can detect reachable assertions before release, reducing the likelihood of exploitation.

finds

A.5.26 item (j) explicitly mandates identifying vulnerabilities and weaknesses that caused or contributed to an incident, so post-incident analysis can locate the specific reachable assertion in code after a triggered DoS — but this is a reactive path that only finds instances which have already been triggered, reported, and investigated to the code level, leaving the bulk of latent CWE-617 instances (never triggered, or triggered without deep root-cause analysis) undiscovered.

prevents

Training developers about secure coding practices (including not using assert() for input validation in production) reduces some instances of reachable assertions, but the practice is fallible and the specific implementation detail requires targeted knowledge that general awareness only partially delivers.

prevents

Secure coding standards explicitly ban the use of assert() or equivalent statements that can be triggered by external input.

finds

A.8.8's reach is DISCLOSURE — it sees only vendor-published flaws, and the disclosed share of any weakness class is a minority, capping `finds` at `partial`. CWE-617 does surface as CVEs (multiple observed examples), so the disclosed portion is findable, but the bulk of latent reachable assertions in deployed code never carries a vendor advisory.

References