First published: Thu Apr 20 2017(Updated: )
A vulnerability in the DNS input packet processor for Cisco Prime Network Registrar could allow an unauthenticated, remote attacker to cause the DNS process to momentarily restart, which could lead to a partial denial of service (DoS) condition on the affected system. The vulnerability is due to incomplete DNS packet header validation when the packet is received by the application. An attacker could exploit this vulnerability by sending a malformed DNS packet to the application. An exploit could allow the attacker to cause the DNS process to restart, which could lead to a DoS condition. This vulnerability affects Cisco Prime Network Registrar on all software versions prior to 8.3.5. Cisco Bug IDs: CSCvb55412.
Credit: ykramarz@cisco.com
Affected Software | Affected Version | How to fix |
---|---|---|
Cisco Prime Network Registrar Major | =8.3.0 | |
Cisco Prime Network Registrar Major | =8.3.1 | |
Cisco Prime Network Registrar Major | =8.3.2 | |
Cisco Prime Network Registrar Major | =8.3.3 | |
Cisco Prime Network Registrar Major | =8.3.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-6613 has been classified as a medium severity vulnerability.
To fix CVE-2017-6613, upgrade Cisco Prime Network Registrar to version 8.3.5 or later.
Exploiting CVE-2017-6613 could lead to a partial denial of service condition due to DNS process interruptions.
Yes, CVE-2017-6613 can be exploited by an unauthenticated remote attacker.
CVE-2017-6613 affects Cisco Prime Network Registrar versions 8.3.0 to 8.3.4.