CVE-2011-0634: Medium severity avahi autoip daemon vulnerability
REJECT DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2011-1002. Reason: This candidate is a reservation duplicate of CVE-2011-1002. Notes: All CVE users should reference CVE-2011-1002 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.
Other sources
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 bug 607297 ( https://bugzilla.redhat.com/showbug.cgi?id=607297 ). 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 avahirecvdnspacketipv4 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.
— Red Hat
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2011-1002. Reason: This candidate is a reservation duplicate of CVE-2011-1002. Notes: All CVE users should reference CVE-2011-1002 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2011-0634?
CVE-2011-0634 is considered a duplicate entry and should be referenced as CVE-2011-1002 for severity details.
How do I fix CVE-2011-0634?
Since CVE-2011-0634 is a duplicate, refer to the remediation steps for CVE-2011-1002.
Which software is affected by CVE-2011-0634?
CVE-2011-0634 affects the Avahi library, specifically versions earlier than 0.6.24.
Why should I not use CVE-2011-0634?
CVE-2011-0634 has been marked as a reject and is a duplicate of CVE-2011-1002, which contains the relevant information.
Is there any public information available on CVE-2011-0634?
Public descriptions and references for CVE-2011-0634 have been removed; please consult CVE-2011-1002 for relevant details.