CVE-2017-3224

Publication date 24 July 2018

Last updated 24 July 2024

Ubuntu priority

Low

Why this priority?

Cvss 3 Severity Score

8.2 · High

Score breakdown

Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).

Read the notes from the security team

Status

Package Ubuntu Release Status
quagga 24.10 oracular Not in release
24.04 LTS noble Not in release
23.10 mantic Not in release
23.04 lunar Not in release
22.10 kinetic Not in release
22.04 LTS jammy Not in release
21.10 impish Ignored end of life
21.04 hirsute Ignored end of life
20.10 groovy Ignored end of life
20.04 LTS focal
Vulnerable
19.10 eoan Ignored end of life
19.04 disco Ignored end of life
18.10 cosmic Ignored end of life
18.04 LTS bionic
Vulnerable
17.10 artful Ignored end of life
17.04 zesty Ignored end of life
16.04 LTS xenial
Vulnerable
14.04 LTS trusty Not in release

Notes

mdeslaur

no upstream fix as of 2018-02-19 while upstream do not have a fix as of 2021-11-22, we can possibly use the fix from frr

Patch details

For informational purposes only. We recommend not to cherry-pick updates. How can I get the fixes?

Package Patch details
quagga

Severity score breakdown

Parameter Value
Base score 8.2 · High
Attack vector Adjacent
Attack complexity High
Privileges required None
User interaction None
Scope Changed
Confidentiality Low
Integrity impact High
Availability impact High
Vector CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H