ID CVE-2006-2224
Summary RIPd in Quagga 0.98 and 0.99 before 20060503 does not properly enforce RIPv2 authentication requirements, which allows remote attackers to modify routing state via RIPv1 RESPONSE packets.
References
Vulnerable Configurations
  • cpe:2.3:a:quagga:quagga_routing_software_suite:0.95
    cpe:2.3:a:quagga:quagga_routing_software_suite:0.95
  • cpe:2.3:a:quagga:quagga_routing_software_suite:0.96.2
    cpe:2.3:a:quagga:quagga_routing_software_suite:0.96.2
  • cpe:2.3:a:quagga:quagga_routing_software_suite:0.96.3
    cpe:2.3:a:quagga:quagga_routing_software_suite:0.96.3
  • cpe:2.3:a:quagga:quagga_routing_software_suite:0.98.5
    cpe:2.3:a:quagga:quagga_routing_software_suite:0.98.5
  • cpe:2.3:a:quagga:quagga_routing_software_suite:0.99.3
    cpe:2.3:a:quagga:quagga_routing_software_suite:0.99.3
CVSS
Base: 5.0 (as of 08-05-2006 - 09:43)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
exploit-db via4
description Quagga Routing Software Suite 0.9x RIPd RIPv1 RESPONSE Packet Route Injection. CVE-2006-2224 . Remote exploit for linux platform
id EDB-ID:27802
last seen 2016-02-03
modified 2006-05-03
published 2006-05-03
reporter Konstantin V. Gavrilenko
source https://www.exploit-db.com/download/27802/
title Quagga Routing Software Suite 0.9x - RIPd RIPv1 RESPONSE Packet Route Injection
nessus via4
  • NASL family Ubuntu Local Security Checks
    NASL id UBUNTU_USN-284-1.NASL
    description Paul Jakma discovered that Quagga's ripd daemon did not properly handle authentication of RIPv1 requests. If the RIPv1 protocol had been disabled, or authentication for RIPv2 had been enabled, ripd still replied to RIPv1 requests, which could lead to information disclosure. (CVE-2006-2223) Paul Jakma also noticed that ripd accepted unauthenticated RIPv1 response packets if RIPv2 was configured to require authentication and both protocols were allowed. A remote attacker could exploit this to inject arbitrary routes. (CVE-2006-2224) Fredrik Widell discovered that Quagga did not properly handle certain invalid 'sh ip bgp' commands. By sending special commands to Quagga, a remote attacker with telnet access to the Quagga server could exploit this to trigger an endless loop in the daemon (Denial of Service). (CVE-2006-2276). Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-08-03
    plugin id 21569
    published 2006-05-16
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=21569
    title Ubuntu 5.04 / 5.10 : quagga vulnerabilities (USN-284-1)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-1059.NASL
    description Konstantin Gavrilenko discovered several vulnerabilities in quagga, the BGP/OSPF/RIP routing daemon. The Common Vulnerabilities and Exposures project identifies the following problems : - CVE-2006-2223 Remote attackers may obtain sensitive information via RIPv1 REQUEST packets even if the quagga has been configured to use MD5 authentication. - CVE-2006-2224 Remote attackers could inject arbitrary routes using the RIPv1 RESPONSE packet even if the quagga has been configured to use MD5 authentication. - CVE-2006-2276 Fredrik Widell discovered that local users can cause a denial of service in a certain sh ip bgp command entered in the telnet interface.
    last seen 2019-02-21
    modified 2018-07-20
    plugin id 22601
    published 2006-10-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=22601
    title Debian DSA-1059-1 : quagga - several vulnerabilities
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-200605-15.NASL
    description The remote host is affected by the vulnerability described in GLSA-200605-15 (Quagga Routing Suite: Multiple vulnerabilities) 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. Impact : 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. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-11-19
    plugin id 21579
    published 2006-05-22
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=21579
    title GLSA-200605-15 : Quagga Routing Suite: Multiple vulnerabilities
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2006-0525.NASL
    description Updated quagga packages that fix several security vulnerabilities are now available. This update has been rated as having moderate security impact by the Red Hat Security Response Team. Quagga manages the TCP/IP based routing protocol. It takes a multi-server and multi-thread approach to resolve the current complexity of the Internet. An information disclosure flaw was found in the way Quagga interprets RIP REQUEST packets. RIPd in Quagga will respond to RIP REQUEST packets for RIP versions that have been disabled or that have authentication enabled, allowing a remote attacker to acquire information about the local network. (CVE-2006-2223) A route injection flaw was found in the way Quagga interprets RIPv1 RESPONSE packets when RIPv2 authentication is enabled. It is possible for a remote attacker to inject arbitrary route information into the RIPd routing tables. This issue does not affect Quagga configurations where only RIPv2 is specified. (CVE-2006-2224) A denial of service flaw was found in Quagga's telnet interface. If an attacker is able to connect to the Quagga telnet interface, it is possible to cause Quagga to consume vast quantities of CPU resources by issuing a malformed 'sh' command. (CVE-2006-2276) Users of Quagga should upgrade to these updated packages, which contain backported patches that correct these issues.
    last seen 2019-02-21
    modified 2018-11-16
    plugin id 21636
    published 2006-06-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=21636
    title RHEL 3 / 4 : quagga (RHSA-2006:0525)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2006-0533.NASL
    description Updated zebra packages that fix several security vulnerabilities are now available. This update has been rated as having moderate security impact by the Red Hat Security Response Team. GNU Zebra is a free software that manages TCP/IP based routing protocol. An information disclosure flaw was found in the way GNU Zebra interprets RIP REQUEST packets. RIPd in GNU Zebra will respond to RIP REQUEST packets for RIP versions that have been disabled or that have authentication enabled, allowing a remote attacker to acquire information about the local network. (CVE-2006-2223) A route injection flaw was found in the way GNU Zebra interprets RIPv1 RESPONSE packets when RIPv2 authentication is enabled. It is possible for a remote attacker to inject arbitrary route information into the RIPd routing tables. This issue does not affect GNU Zebra configurations where only RIPv2 is specified. (CVE-2006-2224) A denial of service flaw was found in GNU Zebra's telnet interface. If an attacker is able to connect to the GNU Zebra telnet interface, it is possible to cause GNU Zebra to consume vast quantities of CPU resources by issuing a malformed 'sh' command. (CVE-2006-2276) Users of GNU Zebra should upgrade to these updated packages, which contain backported patches that correct these issues.
    last seen 2019-02-21
    modified 2018-11-16
    plugin id 21637
    published 2006-06-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=21637
    title RHEL 2.1 : zebra (RHSA-2006:0533)
  • NASL family Misc.
    NASL id QUAGGA_0_99_4.NASL
    description According to its self-reported version number, the installation of Quagga listening on the remote host is affected by multiple vulnerabilities : - An information disclosure vulnerability in RIPD can be triggered by a REQUEST packet, such as SEND UPDATE, on hosts that disable RIPv1 or require plaintext or MD5 authentication. (CVE-2006-2223) - An authentication bypass vulnerability in RIPD may allow unauthenticated, remote attackers to modify routing state via RIPv1 RESPONSE packets. (CVE-2006-2224) - A denial of service vulnerability in Zebra can be triggered by a certain BGP command. (CVE-2006-2276)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 59793
    published 2012-06-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=59793
    title Quagga < 0.98.6 / 0.99.4 Multiple Vulnerabilities
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2006-0525.NASL
    description Updated quagga packages that fix several security vulnerabilities are now available. This update has been rated as having moderate security impact by the Red Hat Security Response Team. Quagga manages the TCP/IP based routing protocol. It takes a multi-server and multi-thread approach to resolve the current complexity of the Internet. An information disclosure flaw was found in the way Quagga interprets RIP REQUEST packets. RIPd in Quagga will respond to RIP REQUEST packets for RIP versions that have been disabled or that have authentication enabled, allowing a remote attacker to acquire information about the local network. (CVE-2006-2223) A route injection flaw was found in the way Quagga interprets RIPv1 RESPONSE packets when RIPv2 authentication is enabled. It is possible for a remote attacker to inject arbitrary route information into the RIPd routing tables. This issue does not affect Quagga configurations where only RIPv2 is specified. (CVE-2006-2224) A denial of service flaw was found in Quagga's telnet interface. If an attacker is able to connect to the Quagga telnet interface, it is possible to cause Quagga to consume vast quantities of CPU resources by issuing a malformed 'sh' command. (CVE-2006-2276) Users of Quagga should upgrade to these updated packages, which contain backported patches that correct these issues.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 21904
    published 2006-07-03
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=21904
    title CentOS 3 / 4 : quagga (CESA-2006:0525)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_QUAGGA-1422.NASL
    description It was possible to bypass RIPv2 authentication requirements by using RIPv1. Since RIPv1 doesn't support authentication at all this update introduces an option to switch off RIPv1 (CVE-2006-2223, CVE-2006-2224).
    last seen 2019-02-21
    modified 2018-07-19
    plugin id 27416
    published 2007-10-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=27416
    title openSUSE 10 Security Update : quagga (quagga-1422)
oval via4
accepted 2013-04-29T04:08:37.401-04:00
class vulnerability
contributors
  • name Aharon Chernin
    organization SCAP.com, LLC
  • name Dragos Prisaca
    organization G2, Inc.
definition_extensions
  • comment The operating system installed on the system is Red Hat Enterprise Linux 3
    oval oval:org.mitre.oval:def:11782
  • comment CentOS Linux 3.x
    oval oval:org.mitre.oval:def:16651
  • comment The operating system installed on the system is Red Hat Enterprise Linux 4
    oval oval:org.mitre.oval:def:11831
  • comment CentOS Linux 4.x
    oval oval:org.mitre.oval:def:16636
  • comment Oracle Linux 4.x
    oval oval:org.mitre.oval:def:15990
description RIPd in Quagga 0.98 and 0.99 before 20060503 does not properly enforce RIPv2 authentication requirements, which allows remote attackers to modify routing state via RIPv1 RESPONSE packets.
family unix
id oval:org.mitre.oval:def:10775
status accepted
submitted 2010-07-09T03:56:16-04:00
title RIPd in Quagga 0.98 and 0.99 before 20060503 does not properly enforce RIPv2 authentication requirements, which allows remote attackers to modify routing state via RIPv1 RESPONSE packets.
version 23
redhat via4
advisories
  • rhsa
    id RHSA-2006:0525
  • rhsa
    id RHSA-2006:0533
refmap via4
bid 17808
bugtraq
  • 20060503 Quagga RIPD unauthenticated route injection
  • 20060503 Re: Quagga RIPD unauthenticated route injection
confirm http://bugzilla.quagga.net/show_bug.cgi?id=262
debian DSA-1059
gentoo GLSA-200605-15
osvdb 25225
sectrack 1016204
secunia
  • 19910
  • 20137
  • 20138
  • 20221
  • 20420
  • 20421
  • 20782
  • 21159
sgi 20060602-01-U
suse SUSE-SR:2006:017
ubuntu USN-284-1
xf quagga-ripd-ripv1-response-security-bypass(26251)
Last major update 31-03-2011 - 00:00
Published 05-05-2006 - 15:02
Last modified 18-10-2018 - 12:38
Back to Top