8.2
CWE
345 354
Advisory Published
Updated

CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine LSA recency in affected Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages)

First published: Tue Jul 24 2018(Updated: )

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

Credit: cret@cert.org

Affected SoftwareAffected VersionHow to fix
Quagga Quagga
SUSE openSUSE
Suse Suse Linux
Redhat Package Manager

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the vulnerability ID?

    The vulnerability ID is CVE-2017-3224.

  • What is the title of the vulnerability?

    The title of the vulnerability is 'Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber.'

  • How does the vulnerability affect Quagga Quagga?

    Quagga Quagga is affected by the vulnerability.

  • How does the vulnerability affect SUSE openSUSE?

    SUSE openSUSE is affected by the vulnerability.

  • How does the vulnerability affect Suse Suse Linux?

    Suse Suse Linux is affected by the vulnerability.

  • How does the vulnerability affect Redhat Package Manager?

    Redhat Package Manager is affected by the vulnerability.

  • What is the severity of CVE-2017-3224?

    The severity of CVE-2017-3224 is high with a severity value of 8.2.

  • What is the Common Weakness Enumeration (CWE) ID for CVE-2017-3224?

    The Common Weakness Enumeration (CWE) ID for CVE-2017-3224 is 345 and 354.

  • Where can I find more information about CVE-2017-3224?

    More information about CVE-2017-3224 can be found at this link: https://www.kb.cert.org/vuls/id/793496

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203