Quagga update to 1.2.3 fyi

mudmanc4

Overview

The Quagga BGP daemon bpgd prior to version 1.2.3 may be vulnerable to multiple issues that may result in denial of service, information disclosure, or remote code execution.
Description

CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer - CVE-2018-5378 (Quagga-2018-0543)

The Quagga BGP daemon, bgpd, does not properly bounds check the data sent with a NOTIFY to a peer, if an attribute length is invalid. Arbitrary data from the bgpd process may be sent over the network to a peer and/or it may crash.

CWE-415: Double Free - CVE-2018-5379 (Quagga-2018-1114)

The Quagga BGP daemon, bgpd, can double-free memory when processing certain forms of UPDATE message, containing cluster-list and/or unknown attributes.

CWE-125: Out-of-bounds Read - CVE-2018-5380 (Quagga-2018-1550)

The Quagga BGP daemon, bgpd, can overrun internal BGP code-to-string conversion tables used for debug by 1 pointer value, based on input.

CWE-228: Improper Handling of Syntactically Invalid Structure - CVE-2018-5381 (Quagga-2018-1975)

The Quagga BGP daemon, bgpd, had a bug in its parsing of "Capabilities" in BGP OPEN messages, in the bgp_packet.c:bgp_capability_msg_parse function. The parser can enter an infinite loop on invalid capabilities if a Multi-Protocol capability does not have a recognized AFI/SAFI.

For more information, please see Quagga's version 1.2.3 release announcement.

The CVSS score below is based on CVE-2018-5379.
Impact

An unauthenticated, remote attacker may be able to use crafted input to result in a crash of bgpd or even allow a remote attacker to gain control of an affected bgpd process.
Solution

Apply an update

Quagga has released version 1.2.3 to address these issues. Affected users should apply an update as soon as possible.

http://www.kb.cert.org/vuls/id/940439

jimp

We'll get that updated. It looks like all of those are all for BGP though, not a lot of quagga BGP users out there on pfSense since it's only supported via raw config.

In the meantime, consider switching to FRR instead of using quagga.

awebster

Just a general observation… Quagga is for all intents and purposes a dead project, and FRR started life as a fork of Quagga, so it is possible the same vulnerabilities are in FRR too, unless of course FRR devs have dealt with them in the past.

jimp

Or, perhaps FRR found and fixed these long ago… (Like https://vuxml.freebsd.org/freebsd/bf266183-cec7-11e7-af2d-2047478f2f70.html seems suspiciously close to one of the current Quagga issues)

Or one of the many patches that the FRR devs couldn't get quagga to accept fixed it.

If FRR is also vulnerable, I'm certain they'll put out and update, and we'll update that, too.

donaldsharp

FRR found and fixed the issues last year. After discussion with our security experts when we ran across these issues we decided to not issue a CVE