# CVE-2011-1002: avahi-core/socket.c in avahi-daemon in Avahi before 0.6.29 allows remote attackers to cause a denial of service (infinite loop) via an empty - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 22 Feb 2011 - **Updated:** 6 Aug 2024 - **Also known as:** CVE-2011-0634, DEBIAN-CVE-2011-1002, DSA-2174-1, GHSA-mqr3-725g-5qgw, RHSA-2011:0436, RHSA-2011:0779 ## What is CVE-2011-1002? CVE-2011-1002 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 22 Feb 2011. ### Official description avahi-core/socket.c in avahi-daemon in Avahi before 0.6.29 allows remote attackers to cause a denial of service (infinite loop) via an empty mDNS (1) IPv4 or (2) IPv6 UDP packet to port 5353. NOTE: this vulnerability exists because of an incorrect fix for CVE-2010-2244. Weakness: CWE-835 (Loop with Unreachable Exit Condition) ## Which versions are affected by CVE-2011-1002? It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `avahi` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-compat-howl` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-compat-howl-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-compat-libdns_sd` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-compat-libdns_sd-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-glib` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-glib-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-qt3` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-qt3-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi-tools` | Red Hat:enterprise_linux:5::server | All versions | 0:0.6.16-10.el5_6 | | `avahi` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-autoipd` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-compat-howl` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-compat-howl-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-compat-libdns_sd` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-compat-libdns_sd-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-dnsconfd` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-glib` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-glib-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-gobject` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-gobject-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-qt3` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-qt3-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-qt4` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-qt4-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-tools` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-ui` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-ui-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi-ui-tools` | Red Hat:enterprise_linux:6::client | All versions | 0:0.6.25-11.el6 | | `avahi` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.6.25-11.el6 | | `avahi-autoipd` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.6.25-11.el6 | | `avahi-compat-howl` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.6.25-11.el6 | | `avahi-compat-howl-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.6.25-11.el6 | | `avahi-compat-libdns_sd` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.6.25-11.el6 | | `avahi-compat-libdns_sd-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.6.25-11.el6 | Products: Avahi Avahi, Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Redhat Enterprise Linux. ## How do I fix CVE-2011-1002? Upgrade to a fixed version. ## Is CVE-2011-1002 being exploited? There is no known exploitation of CVE-2011-1002 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2017-6519](https://insights.sbomify.com/CVE-2017-6519/): Denial of service in n/a (critical 9.1) - [CVE-2021-26720](https://insights.sbomify.com/CVE-2021-26720/): Path traversal in n/a (high 7.8) - [CVE-2026-24401](https://insights.sbomify.com/CVE-2026-24401/): Avahi has Uncontrolled Recursion in lookup_handle_cname function (medium 6.5) - [CVE-2025-68468](https://insights.sbomify.com/CVE-2025-68468/): Avahi has a reachable assertion in lookup_multicast_callback (medium 6.5) - [CVE-2025-68471](https://insights.sbomify.com/CVE-2025-68471/): Avahi has a reachable assertion in lookup_start (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2011-1002 and fix it if it is affected. What it is: CVE-2011-1002 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 22 Feb 2011. Exploitation: There is no known exploitation of CVE-2011-1002 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2011-1002/ (Markdown: https://insights.sbomify.com/CVE-2011-1002/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2011-1002 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-1002 - OSV: https://osv.dev/vulnerability/CVE-2011-1002 --- From sbomify Insights: https://insights.sbomify.com/CVE-2011-1002/ Summaries are generated and may contain mistakes; the official description above is the record.