CVE-2017-3224 Detail
Current 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).
Source:
MITRE
Description Last Modified:
07/24/2018
View Analysis Description
Analysis 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).
Source:
MITRE
Description Last Modified:
07/24/2018
Impact
CVSS v3.0 Severity and Metrics:
Base Score:
8.2 HIGH
Vector:
AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H
(V3 legend)
Impact Score:
6.0
Exploitability Score:
1.6
Attack Vector (AV):
Adjacent
Attack Complexity (AC):
High
Privileges Required (PR):
None
User Interaction (UI):
None
Scope (S):
Changed
Confidentiality (C):
Low
Integrity (I):
High
Availability (A):
High
CVSS v2.0 Severity and Metrics:
Base Score:
4.3 MEDIUM
Vector:
(AV:A/AC:M/Au:N/C:N/I:P/A:P)
(V2 legend)
Impact Subscore:
4.9
Exploitability Subscore:
5.5
Access Vector (AV):
Local_Network
Access Complexity (AC):
Medium
Authentication (AU):
None
Confidentiality (C):
None
Integrity (I):
Partial
Availability (A):
Partial
Additional Information:
Allows unauthorized modification
Allows disruption of service
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because
they may have information that would be of interest to you. No inferences should be drawn on account of other sites
being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose.
NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further,
NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about
this page to nvd@nist.gov.
Technical Details
Vulnerability Type
(View All)
- Insufficient Verification of Data Authenticity (CWE-345)
Change History
1 change record found
- show changes
Initial Analysis -
10/4/2018 10:57:36 AM
| Action |
Type |
Old Value |
New Value |
| Added |
CPE Configuration |
|
OR
*cpe:2.3:a:quagga:quagga:-:*:*:*:*:*:*:* |
| Added |
CPE Configuration |
|
OR
*cpe:2.3:a:redhat:package_manager:-:*:*:*:*:*:*:* |
| Added |
CPE Configuration |
|
OR
*cpe:2.3:o:suse:opensuse:-:*:*:*:*:*:*:*
*cpe:2.3:o:suse:suse_linux:-:*:*:*:*:*:*:* |
| Added |
CVSS V2 |
|
(AV:A/AC:M/Au:N/C:N/I:P/A:P) |
| Added |
CVSS V3 |
|
AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H |
| Added |
CWE |
|
CWE-345 |
| Changed |
Reference Type |
https://www.kb.cert.org/vuls/id/793496 No Types Assigned |
https://www.kb.cert.org/vuls/id/793496 Third Party Advisory, US Government Resource |
Quick Info
CVE Dictionary Entry:
CVE-2017-3224
NVD Published Date:
07/24/2018
NVD Last Modified:
10/04/2018
|