CVE-2025-59529

Source
https://cve.org/CVERecord?id=CVE-2025-59529
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-59529.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-59529
Aliases
  • GHSA-73wf-3xmj-x82q
Downstream
Related
Published
2025-12-18T20:25:31.499Z
Modified
2026-04-10T05:34:10.171253Z
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
simple protocol server ignores accepts unlimited connections and logs failures without limit
Details

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In versions up to and including 0.9-rc2, the simple protocol server ignores the documented client limit and accepts unlimited connections, allowing for easy local DoS. Although CLIENTS_MAX is defined, server_work() unconditionally accept()s and client_new() always appends the new client and increments n_clients. There is no check against the limit. When client cannot be accepted as a result of maximal socket number of avahi-daemon, it logs unconditionally error per each connection. Unprivileged local users can exhaust daemon memory and file descriptors, causing a denial of service system-wide for mDNS/DNS-SD. Exhausting local file descriptors causes increased system load caused by logging errors of each of request. Overloading prevents glibc calls using nss-mdns plugins to resolve *.local. names and link-local addresses. As of time of publication, no known patched versions are available, but a candidate fix is available in pull request 808, and some workarounds are available. Simple clients are offered for nss-mdns package functionality. It is not possible to disable the unix socket /run/avahi-daemon/socket, but resolution requests received via DBus are not affected directly. Tools avahi-resolve, avahi-resolve-address and avahi-resolve-host-name are not affected, they use DBus interface. It is possible to change permissions of unix socket after avahi-daemon is started. But avahi-daemon does not provide any configuration for it. Additional access restrictions like SELinux can also prevent unwanted tools to access the socket and keep resolution working for trusted users.

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/59xxx/CVE-2025-59529.json",
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
        "CWE-400"
    ]
}
References

Affected packages

Git / github.com/avahi/avahi

Affected ranges

Type
GIT
Repo
https://github.com/avahi/avahi
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Last affected
Database specific
{
    "versions": [
        {
            "introduced": "0"
        },
        {
            "last_affected": "0.9-rc2"
        }
    ]
}

Affected versions

0.*
0.6.32-rc
v0.*
v0.6.23
v0.6.24
v0.6.25
v0.6.26
v0.6.27
v0.6.28
v0.6.29
v0.6.30
v0.6.31
v0.6.32
v0.7
v0.8
v0.9-rc1
v0.9-rc2

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-59529.json"

Git / github.com/lathiat/avahi

Affected ranges

Type
GIT
Repo
https://github.com/lathiat/avahi
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Last affected
Database specific
{
    "versions": [
        {
            "introduced": "0"
        },
        {
            "last_affected": "0.9-rc1"
        }
    ]
}

Affected versions

0.*
0.6.32-rc
v0.*
v0.6.23
v0.6.24
v0.6.25
v0.6.26
v0.6.27
v0.6.28
v0.6.29
v0.6.30
v0.6.31
v0.6.32
v0.7
v0.8
v0.9-rc1

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-59529.json"