Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2018-0421 | First vendor Publication | 2018-10-05 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 8.6 | ||
Base Score | 8.6 | Environmental Score | 8.6 |
impact SubScore | 4 | Temporal Score | 8.6 |
Exploitabality Sub Score | 3.9 | ||
Attack Vector | Network | Attack Complexity | Low |
Privileges Required | None | User Interaction | None |
Scope | Changed | Confidentiality Impact | None |
Integrity Impact | None | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:N/AC:L/Au:N/C:N/I:N/A:P) | |||
---|---|---|---|
Cvss Base Score | 5 | Attack Range | Network |
Cvss Impact Score | 2.9 | Attack Complexity | Low |
Cvss Expoit Score | 10 | Authentication | None Required |
Calculate full CVSS 2.0 Vectors scores |
Detail
A vulnerability in TCP connection management in Cisco Prime Access Registrar could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition when the application unexpectedly restarts. The vulnerability is due to incorrect handling of incoming TCP SYN packets to specific listening ports. The improper handling of the TCP SYN packets could cause a system file description to be allocated and not freed. An attacker could exploit this vulnerability by sending a crafted stream of TCP SYN packets to the application. A successful exploit could allow the attacker to cause the application to eventually restart if a file description cannot be obtained. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0421 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-772 | Missing Release of Resource after Effective Lifetime |
CPE : Common Platform Enumeration
Type | Description | Count |
---|---|---|
Application | 1 | |
Application | 1 |
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2024-11-28 13:10:37 |
|
2021-05-04 13:07:23 |
|
2021-04-22 02:21:12 |
|
2020-05-23 01:05:05 |
|
2019-10-10 05:20:13 |
|
2019-10-03 09:20:41 |
|
2019-01-04 17:19:57 |
|
2018-10-07 17:19:23 |
|
2018-10-05 21:19:40 |
|