Bug 1542992 (CVE-2018-5381) - CVE-2018-5381 quagga: Infinite loop issue triggered by invalid OPEN message allows denial-of-service
Summary: CVE-2018-5381 quagga: Infinite loop issue triggered by invalid OPEN message a...
Alias: CVE-2018-5381
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1546003 1546004
Blocks: 1543001
TreeView+ depends on / blocked
Reported: 2018-02-07 14:18 UTC by Adam Mariš
Modified: 2021-03-11 17:08 UTC (History)
7 users (show)

Fixed In Version: quagga 1.2.3
Doc Type: If docs needed, set a value
Doc Text:
An infinite loop vulnerability was discovered in Quagga. A BGP peer could send specially crafted packets that would cause the daemon to enter an infinite loop, denying service and consuming CPU until it is restarted.
Clone Of:
Last Closed: 2019-06-08 03:39:29 UTC

Attachments (Terms of Use)
Upstream patch (1.19 KB, patch)
2018-02-07 14:22 UTC, Adam Mariš
no flags Details | Diff

Description Adam Mariš 2018-02-07 14:18:34 UTC
The Quagga BGP daemon, bgpd, can enter an infinite loop if sent an invalid
OPEN message by a configured peer.

This problem is triggerable by packets from a configured peer.

When triggered, the bgpd daemon enters an infinite loop and cease to respond
to any other events.  BGP sessions will drop and not be reestablished.  The
CLI interface will be unresponsive.  The bgpd daemon will stay in this state
until it is restarted.

Affects versions of quagga since 0.99.9

If "override-capability" neighbour option is set, all versions are affected.

Comment 1 Adam Mariš 2018-02-07 14:18:38 UTC

Name: the Quagga project

Comment 3 Adam Mariš 2018-02-07 14:22:46 UTC
Created attachment 1392683 [details]
Upstream patch

Comment 4 Doran Moppert 2018-02-13 04:15:30 UTC
External References:


Comment 5 Doran Moppert 2018-02-16 04:37:17 UTC
Created quagga tracking bugs for this issue:

Affects: fedora-all [bug 1546004]

Note You need to log in before you can comment on or make changes to this bug.