glsa-200605-15.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200605-15">
  <title>Quagga Routing Suite: Multiple vulnerabilities</title>
  <synopsis>
    Quagga's RIP daemon allows the injection of routes and the disclosure of
    routing information. The BGP daemon is vulnerable to a Denial of Service.
  </synopsis>
  <product type="ebuild">quagga</product>
  <announced>2006-05-21</announced>
  <revised>2006-05-21: 01</revised>
  <bug>132353</bug>
  <access>remote</access>
  <affected>
    <package name="net-misc/quagga" auto="yes" arch="*">
      <unaffected range="ge">0.98.6-r1</unaffected>
      <vulnerable range="lt">0.98.6-r1</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    The Quagga Routing Suite implements three major routing protocols:
    RIP (v1/v2/v3), OSPF (v2/v3) and BGP4.
    </p>
  </background>
  <description>
    <p>
    Konstantin V. Gavrilenko discovered two flaws in the Routing
    Information Protocol (RIP) daemon that allow the processing of RIP v1
    packets (carrying no authentication) even when the daemon is configured
    to use MD5 authentication or, in another case, even if RIP v1 is
    completely disabled. Additionally, Fredrik Widell reported that the
    Border Gateway Protocol (BGP) daemon contains a flaw that makes it lock
    up and use all available CPU when a specific command is issued from the
    telnet interface.
    </p>
  </description>
  <impact type="normal">
    <p>
    By sending RIP v1 response packets, an unauthenticated attacker
    can alter the routing table of a router running Quagga's RIP daemon and
    disclose routing information. Additionally, it is possible to lock up
    the BGP daemon from the telnet interface.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All Quagga users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=net-misc/quagga-0.98.6-r1"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2223">CVE-2006-2223</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2224">CVE-2006-2224</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2276">CVE-2006-2276</uri>
    <uri link="http://www.quagga.net/news2.php?y=2006&amp;m=5&amp;d=8#id1147115280">Official release information</uri>
  </references>
  <metadata tag="requester" timestamp="2006-05-15T05:35:52Z">
    jaervosz
  </metadata>
  <metadata tag="bugReady" timestamp="2006-05-15T16:38:23Z">
    koon
  </metadata>
  <metadata tag="submitter" timestamp="2006-05-16T05:49:19Z">
    frilled
  </metadata>
</glsa>