CVEvulnerability

CVE-2017-3224

8.2 HIGH Published 2018-07-24 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2018-07-24
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.0 ([email protected])
8.2 HIGH — CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H
CVSS 2.0 ([email protected])
4.3 MEDIUM — AV:A/AC:M/Au:N/C:N/I:P/A:P
Weaknesses
CWE-345, CWE-354

Description

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).

Affected configurations

• quagga quagga • suse opensuse • suse suse linux • redhat package manager

Related

Weakness · CWE (2)

  • CWE-345 Insufficient Verification of Data Authenticity weakness
  • CWE-354 Improper Validation of Integrity Check Value weakness

References