# What is CVE-2017-3224? > CVE-2017-3224 is a high-severity flaw (CVSS 8.2) in Quagga, published on 24 July 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.1%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-3224 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 46 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes. - **Severity:** High (CVSS 8.2 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 1.1% (latest exploit-likelihood forecast) - **Published:** 24 July 2018 - **Record last updated:** 9 October 2019 - **Main product:** Quagga - **Affected products:** 4 ## What is CVE-2017-3224? In plain terms An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can change data and take it offline. ### The official 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). ### What kind of flaw is it? - CWE-345: Insufficient Verification of Data Authenticity - CWE-354: Improper Validation of Integrity Check Value ### How an attack on it works - Where an attacker can be: On the same local network - How hard it is to pull off: Hard: conditions must line up - Login needed first: No login needed - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can change data and take it offline Severity vector: `CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H` ## Is CVE-2017-3224 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.1%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 1.1%, 1.1%, 1.1%, 1.1%, 1.1%, 1.1%, 1.1%. ### Timeline - 24 July 2018: Published - 9 October 2019: Record last updated ### How Precursor Intelligence ranks it CVE-2017-3224 scores **46 out of 100 (Medium)**, with the action "Plan remediation". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2017-3224? The published record lists 4 products. - [Quagga](https://www.precursorintelligence.com/product/quagga/quagga) by [Quagga](https://www.precursorintelligence.com/vendors/quagga) (Application): version not specified - [Opensuse](https://www.precursorintelligence.com/product/suse/opensuse) by [Suse](https://www.precursorintelligence.com/vendors/suse) (Operating system): version not specified - [Package Manager](https://www.precursorintelligence.com/product/redhat/package_manager) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Application): version not specified - [Suse Linux](https://www.precursorintelligence.com/product/suse/suse_linux) by [Suse](https://www.precursorintelligence.com/vendors/suse) (Operating system): version not specified ## How do I fix CVE-2017-3224? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [kb.cert.org](https://www.kb.cert.org/vuls/id/793496) (Third-party advisory, Government resource) ## Questions ### What is CVE-2017-3224? CVE-2017-3224 is a high-severity flaw in Quagga, published on 24 July 2018. An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can change data and take it offline. ### How serious is CVE-2017-3224? It scores 8.2 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2017-3224 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2017-3224 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.1%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2017-3224 affect? For Quagga: version not specified. The record lists 4 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2017-3224? Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2017-3224 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact