CVE-2017-7507

What it actually does

NULL pointer dereference during decoding of a TLS status response extension with valid contents triggers an unhandled crash in the GnuTLS library.

Why it matters to the business

Remote attackers can force GnuTLS-based servers to terminate, producing denial-of-service outages and service disruption until the process is restarted.

How an attack unfolds

An unauthenticated remote attacker crafts a TLS handshake containing a status response extension and sends it to a GnuTLS server; the library dereferences a null pointer while processing the extension and crashes.

How to fix it

Upgrade GnuTLS to a version newer than 3.5.12 that contains the NULL-pointer fix; rebuild and restart all dependent server applications; test TLS handshake functionality after upgrade.

How to confirm the fix worked

Confirm the installed GnuTLS shared library or package reports a version greater than 3.5.12; run automated TLS handshake tests that exercise the status_request extension and verify the server remains stable.

Typical attack path

1. Attacker establishes a TCP connection to a TLS service using GnuTLS
2. Attacker sends a ClientHello that includes a status_request extension with crafted but syntactically valid contents
3. GnuTLS server processes the extension during handshake and hits the null dereference
4. Server process crashes, closing all active connections

How to detect it

Review service and system logs for sudden GnuTLS process terminations or segmentation faults occurring during TLS handshakes; correlate with inbound TLS traffic that contains status_request extensions.

What your security team should do

• Inventory all systems and containers that link against GnuTLS and prioritize upgrades
• Apply the newest GnuTLS package available from the operating-system or language distribution
• Monitor for repeated abrupt terminations of GnuTLS-based services as an operational indicator