Menu

Star on GitHub · 3.2k

CVE-2015-6251

5.0 · MEDIUM

Double free vulnerability in GnuTLS before 3.3.17 and 3.4.x before 3.4.4 allows remote attackers to cause a denial of service via a long DistinguishedName (DN) entry in a certificate.

Published Aug 24, 2015gnuEPSS 19.03%

Overview

CVE-2015-6251 is a medium-severity vulnerability affecting gnu gnutls. It was published on August 24, 2015 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

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

Technical description

Double free vulnerability in GnuTLS before 3.3.17 and 3.4.x before 3.4.4 allows remote attackers to cause a denial of service via a long DistinguishedName (DN) entry in a certificate.

Remediation

Check the references section for vendor advisories and patches from gnu. Update gnutls to the latest patched version. 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.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2015-6251?

CVE-2015-6251 is a medium-severity vulnerability affecting gnu gnutls. It was published on August 24, 2015 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

How severe is CVE-2015-6251?

This vulnerability has a CVSS 2.0 base score of 5.0, 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-2015-6251?

Check the references section for vendor advisories and patches from gnu. Update gnutls to the latest patched version. 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-2015-6251?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2015-6251 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 2015

View all