CVE-2024-1062

What it actually does

A heap buffer overflow occurs when writing a value larger than 256 characters to log_entry_attr, resulting in memory corruption that manifests as a denial of service.

Why it matters to the business

Service availability can be disrupted in directory environments with no risk to data confidentiality or integrity; low EPSS and absence from KEV indicate limited immediate threat, though the widespread use of the affected component warrants prompt attention to prevent operational downtime.

How an attack unfolds

An attacker with local low-privileged access supplies an oversized attribute value during logging operations to trigger the heap overflow and crash the process; no named threat actors or ransomware campaigns are associated with this issue.

How to fix it

Upgrade gnutls/gnutls (GIT) to the fixed commit 3a88ae123536f7e39f831a47884ae070ce162688.

How to confirm the fix worked

Confirm the installed version matches or exceeds commit 3a88ae123536f7e39f831a47884ae070ce162688 and test logging of attribute values longer than 256 characters to verify stability.

Typical attack path

1. Obtain local access with low privileges on the target system
2. Interact with the logging path that processes log_entry_attr
3. Provide an attribute value exceeding 256 characters
4. Trigger heap overflow leading to denial of service

How to detect it

Examine process crash logs and service restart events for the affected component; search audit trails for log entries containing unusually long attribute values near the time of incidents.

What your security team should do

• Apply the fixed commit 3a88ae123536f7e39f831a47884ae070ce162688 without delay
• Monitor service availability metrics for unexpected restarts
• Review and constrain attribute value lengths in logging configurations where feasible