CVE-2018-5379
CVE-2018-5379 Vulnerability Analysis & Exploit Intelligence
The Quagga BGP daemon (bgpd) prior to version 1.2.3 can double-free memory when processing certain forms of UPDATE message, containing cluster-list and/or unknown attributes. A successful attack could cause a denial of service or potentially allow an attacker to execute arbitrary code.
Published Updated Sources: cvelistV5, certcc
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
38%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-415
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /or.
References
10 on the record
- usn.ubuntu.com/3573-1/
vendor-advisory, x_refsource_UBUNTU
- www.debian.org/security/2018/dsa-4115
vendor-advisory, x_refsource_DEBIAN
- www.securityfocus.com/bid/103105
vdb-entry, x_refsource_BID
- savannah.nongnu.org/forum/forum.php?forum_id=9095
x_refsource_CONFIRM
- security.gentoo.org/glsa/201804-17
vendor-advisory, x_refsource_GENTOO
- gogs.quagga.net/Quagga/quagga/src/master/doc/security/Quagga-2018-1114.txt
x_refsource_CONFIRM
- lists.debian.org/debian-lts-announce/2018/02/msg00021.html
mailing-list, x_refsource_MLIST
- www.kb.cert.org/vuls/id/940439
third-party-advisory, x_refsource_CERT-VN
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.