CVE-2024-52616 | Avahi: avahi wide-area dns predictable transaction ids

A flaw was found in the Avahi-daemon, where it initializes DNS transaction IDs randomly only once at startup, incrementing them sequentially after that. This predictable behavior facilitates DNS spoofing attacks, allowing attackers to guess transaction IDs.

Published: 2024-11-21 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-52616 is rated Low Risk (29.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.09%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-52616

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-30 0.33% 0.09% -0.24%
2 2025-12-24 0.16% 0.33% +0.16%
3 2025-08-17 — 0.16% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-52616

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2024-52616

OS Trackers for CVE-2024-52616

vendor priority summary link
alpine — CVE-2024-52616: 1 source package rows (avahi); 2 state rows across 2 repos (3.22-main, edge-main); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2024-52616
debian not yet assigned CVE-2024-52616 not yet assigned priority: Debian including 1 source packages (avahi), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2024-52616
redhat medium — https://access.redhat.com/security/cve/CVE-2024-52616
suse medium CVE-2024-52616 severity moderate: SUSE including 396 source package names (2.0.4-5.5.212:avahi-0.8-150400.7.20.1, 2.0.4-5.5.212:libavahi-common3-0.8-150400.7.20.1, …), 987 product×package rows across 258 product lines (Container suse/kiosk/firefox-esr, Container suse/manager/5.0/x86_64/server, … (258 product lines)): Fixed 766, Known Affected 221. https://www.suse.com/security/cve/CVE-2024-52616/
ubuntu low CVE-2024-52616 low priority: Ubuntu including 1 source packages (avahi), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needed 6, ignored 3, released 1. https://ubuntu.com/security/CVE-2024-52616

Affected software / configurations for CVE-2024-52616

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-52616

cvelogic Threat Intelligence