CVE-2018-5378: high-severity vulnerability in Quagga bgpd
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
43Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 74%
What the vendors declare (VEX)
Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.
Red HatVEX document ↗
Not affected
4 products (12 components) — because the vulnerable code is not present in the product
Red Hat Enterprise Linux 6 · Red Hat Enterprise Linux 7 · Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux 5
The Quagga BGP daemon (bgpd) prior to version 1.2.3 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 bgpd may crash.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
Affected products
Quagga · bgpdRelated CVEs — Quagga bgpd
In the same product, most dangerous first.
References
http://savannah.nongnu.org/forum/forum.php?forum_id=9095https://gogs.quagga.net/Quagga/quagga/src/master/doc/security/Quagga-2018-0543.txthttps://security.gentoo.org/glsa/201804-17https://usn.ubuntu.com/3573-1/https://www.debian.org/security/2018/dsa-4115http://www.kb.cert.org/vuls/id/940439