CVE-2023-38469
Avahi ≤ 0.9
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS 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-38469 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
- 🇪🇺 ENISA EUVD: EUVD-2023-42285
Vulnerability Data
A vulnerability was found in Avahi, where a reachable assertion exists in avahi_dns_packet_append_record.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
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.
Secure SDLC practices directly prevent unsafe assertions from being coded in reachable paths.
Runtime monitoring of software can detect assertion-triggered crashes as adverse events.
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.
Security testing in development can detect reachable assertions before release, reducing the likelihood of exploitation.
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.
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.
Secure coding standards explicitly ban the use of assert() or equivalent statements that can be triggered by external input.
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.