CVE-2018-5378: Quagga bgpd vulnerability
Quagga · bgpd
Vendor fix available · Affected: Quagga bgpd · Exploitation: likely to be exploited (10% or more)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 99% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Quagga · bgpdfrom bpgd before 1.2.3
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Quagga
- Published
- February 2018
CoverageNo articles yet
No CyberSIXT article names CVE-2018-5378 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-119cwe.mitre.org
- Vendor advisoryusn.ubuntu.com
- Vendor advisorydebian.org
- Vendor advisorysecurity.gentoo.org
- gogs.quagga.net/Quagga/quagga/src/master/doc/security/Quagga-201gogs.quagga.net
- savannah.nongnu.org/forum/forum.php?forum_id=9095savannah.nongnu.org
- Third-party advisorykb.cert.org