Menu

Star on GitHub · 3.2k

CVE-2016-2088

6.8 · MEDIUM

resolver.c in named in ISC BIND 9.10.x before 9.10.3-P4, when DNS cookies are enabled, allows remote attackers to cause a denial of service (INSIST assertion failure and daemon exit) via a malforme…

Published Mar 9, 2016CWE-20EPSS 22.79%

Overview

CVE-2016-2088 is a medium-severity vulnerability. It was published on March 9, 2016 and has a CVSS 3.0 base score of 6.8 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 6.8, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

resolver.c in named in ISC BIND 9.10.x before 9.10.3-P4, when DNS cookies are enabled, allows remote attackers to cause a denial of service (INSIST assertion failure and daemon exit) via a malformed packet with more than one cookie option.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-2088?

CVE-2016-2088 is a medium-severity vulnerability. It was published on March 9, 2016 and has a CVSS 3.0 base score of 6.8 (MEDIUM).

How severe is CVE-2016-2088?

This vulnerability has a CVSS 3.0 base score of 6.8, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-2088?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-2088?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-2088 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2016

View all