CVE-2023-38469VulnerabilityPublished 2 Nov 2023Updated 3 Nov 2025

CVE-2023-38469: avahi · Reachable Assertion

Affects avahiSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor official Avahi and Linux distribution security advisories for patches addressing CVE-2023-38469 and apply updates promptly once available. 2. Restrict local access to systems running Avahi, especially in multi-user environments, to trusted personnel only. 3. Implement network segmentation to isolate critical systems and reduce the attack surface for local exploits. 4. Disable Avahi service on systems where zero-configuration networking is not required to eliminate exposure. 5. Employ host-based intrusion detection systems to monitor for unusual crashes or service disruptions related to Avahi. 6. Conduct regular audits of local network services and permissions to ensure minimal privilege and access controls. 7. Educate system administrators about the vulnerability and encourage vigilance for signs of denial of service or instability in Avahi-dependent services. 8. Consider alternative service discovery mechanisms if Avahi is critical and patches are delayed.

Description

A vulnerability was found in Avahi, where a reachable assertion exists in avahi_dns_packet_append_record.

Impact

For European organizations, the primary impact of CVE-2023-38469 is a denial of service affecting network service discovery on local networks. This can disrupt applications and services relying on Avahi for automatic detection and configuration, potentially causing operational delays or failures in environments where zero-configuration networking is critical. While confidentiality and integrity are not impacted, availability degradation can affect user experience and automated network management tasks. Organizations with large Linux deployments, IoT devices, or embedded systems using Avahi could see increased risk. Critical infrastructure sectors such as manufacturing, telecommunications, and public services that depend on reliable local network service discovery may experience operational disruptions. Since exploitation requires local access, the threat is more significant in environments where untrusted users or compromised hosts have local network access. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 23:39 UTC

Technical details

References

Community reviews

Related threats