CVE-2018-5379

UnknownEPSS 39.46%

Last modified

CVE-2018-5379 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 39.46% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
39.46%

98.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
QuaggaQuagga<= 1.2.2
DebianDebian Linux7.0
DebianDebian Linux8.0
DebianDebian Linux9.0
CanonicalUbuntu Linux14.04
CanonicalUbuntu Linux16.04
CanonicalUbuntu Linux17.10
RedhatEnterprise Linux Server7.0
RedhatEnterprise Linux Server Aus7.4
RedhatEnterprise Linux Server Aus7.6
RedhatEnterprise Linux Server Eus7.4
RedhatEnterprise Linux Server Eus7.5
RedhatEnterprise Linux Server Eus7.6
RedhatEnterprise Linux Server Tus7.4
RedhatEnterprise Linux Server Tus7.6
RedhatEnterprise Linux Workstation7.0
SiemensRuggedcom Rox Ii Firmware< 2.13.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2018-5379?
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.
How severe is CVE-2018-5379?
Severity scoring for CVE-2018-5379 is pending analysis. The EPSS model estimates a 39.46% probability of exploitation in the next 30 days.
How do I fix CVE-2018-5379?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2018-5379?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST