REDHAT-BUG-667187
First published: Tue Jan 04 2011(Updated: )
Description of problem: If a NULL UDP packet is sent to the avahi port 5353 it triggers and infinite loop with all the expected goodies, 100% CPU usage and DOS of avahi. This is due to the fix for <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - DoS (assertion failure) after receiving a packet with corrupted checksum [fedora-all]" href="show_bug.cgi?id=607297">bug 607297</a> ( <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - DoS (assertion failure) after receiving a packet with corrupted checksum [fedora-all]" href="show_bug.cgi?id=607297">https://bugzilla.redhat.com/show_bug.cgi?id=607297</a> ). You can re-open that bug and fix it with something that clears the null message from the socket before going to fail or you can keep this as a separate bug. Version-Release number of selected component (if applicable): all versions of avahi >0.6.24 Steps to Reproduce: Send a null UDP packet to avahi on port 5353. I personally use Scapy but anything will work. Actual results: Infinite loop. Expected results: Packet discarded. Additional info: In avahi_recv_dns_packet_ipv4 the bug fix: if (!ms) goto fail; Doesn't clear out a Null message from the socket before returning. This is reason for the infinite loop.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Avahi AutoIP Daemon | >0.6.24 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=607297
- http://avahi.org/ticket/325
- https://access.redhat.com/security/cve/CVE-2011-0634
- https://access.redhat.com/security/cve/CVE-2011-1002
- https://access.redhat.com/security/cve/CVE-2010-2244
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1002
- http://openwall.com/lists/oss-security/2011/02/18/1
- http://openwall.com/lists/oss-security/2011/02/18/4
- http://git.0pointer.de/?p=avahi.git;a=commit;h=46109dfec75534fe270c0ab902576f685d5ab3a6
- http://www.securityfocus.com/bid/46446
- http://secunia.com/advisories/43361
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-0634
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=679861
- http://git.0pointer.de/?p=avahi.git;a=commitdiff;h=46109dfec75534fe270c0ab902576f685d5ab3a6
- https://rhn.redhat.com/errata/RHSA-2011-0436.html
- https://rhn.redhat.com/errata/RHSA-2011-0779.html
- https://bugzilla.redhat.com/show_bug.cgi?id=667187
Frequently Asked Questions
What is the severity of REDHAT-BUG-667187?
The severity of REDHAT-BUG-667187 is critical due to its potential to cause a denial-of-service condition by consuming 100% CPU usage.
How do I fix REDHAT-BUG-667187?
To fix REDHAT-BUG-667187, upgrade Avahi to a version that is greater than 0.6.24 where the vulnerability is addressed.
What causes the REDHAT-BUG-667187 vulnerability?
The REDHAT-BUG-667187 vulnerability is caused by an infinite loop triggered by a NULL UDP packet sent to the avahi port 5353.
Which versions of Avahi are affected by REDHAT-BUG-667187?
Avahi versions below 0.6.24 are affected by the REDHAT-BUG-667187 vulnerability.
Is REDHAT-BUG-667187 specific to certain operating systems?
Yes, REDHAT-BUG-667187 is primarily associated with systems running Red Hat that utilize the Avahi daemon.
- agent/type
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2011-0634
- agent/first-publish-date
- agent/source
- agent/references
- agent/severity
- agent/description
- agent/event
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/avahi
- canonical/avahi autoip daemon