CVE-2026-110779 in Netatalkinfo

Summary

by MITRE • 11/20/2026

Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 3.1.0 until 4.5.2, sl_createCNIDArray in etc/afpd/spotlight.c assumes every element of kMDQueryItemArray points to an eight-byte uint64_t and copies sizeof(uint64_t) bytes from the indexed p->dd_talloc_array element without validating the element's talloc type or allocation size. An authenticated AFP client with access to a Spotlight-enabled volume can use FPSpotlightRPC to supply a mixed-type sl_array_t containing a shorter boolean, nil, or string element, and an unauthenticated client can reach the same path when the optional guest UAM and a guest-accessible volume are enabled. The resulting eight-byte read extends beyond the shorter element's heap allocation and supplies an internal CNID filter; no confidentiality channel, write primitive, or code execution was demonstrated, while a production crash would require additional heap placement conditions. The container-type validation added for CVE-2023-42464 does not validate each element inside an accepted sl_array_t and therefore does not resolve this issue. This issue is fixed in version 4.5.2.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

Netatalk serves as a critical interoperability layer, enabling Unix-like operating systems to function as file servers for Apple Macintosh clients via the Apple Filing Protocol. Within this architecture, the Spotlight integration component handles metadata indexing and querying, which is essential for maintaining search functionality across networked volumes. A significant vulnerability exists in the sl_createCNIDArray function located within the etc/afpd/spotlight.c source code module. This flaw stems from a fundamental assumption that every element within the kMDQueryItemArray structure points to an eight-byte uint64_t value. The implementation proceeds to copy sizeof(uint64_t) bytes from the indexed p->dd_talloc_array element without performing any validation regarding the talloc type or the actual allocation size of the source data. This lack of rigorous input verification creates a scenario where the application blindly trusts the structure's metadata rather than validating the integrity and dimensions of the underlying memory blocks it intends to access.

The operational impact of this flaw is primarily characterized by an out-of-bounds read vulnerability, which falls under CWE-125 in standard classification systems. An authenticated AFP client possessing access to a Spotlight-enabled volume can exploit this condition through the FPSpotlightRPC interface by supplying a mixed-type sl_array_t that contains elements shorter than eight bytes, such as boolean values, nil pointers, or string data structures. Furthermore, if an administrator has enabled optional guest User Authentication Modules and designated volumes for guest access, unauthenticated remote attackers can also trigger this code path. The immediate consequence of exploiting this flaw is a heap-based buffer over-read where the application reads beyond the bounds of the allocated memory block associated with the shorter element. This action exposes internal CNID filter data to the attacker, potentially leading to information disclosure regarding the server's internal state and file indexing mechanisms.

While the vulnerability allows for unauthorized reading of sensitive internal structures, it does not inherently provide a write primitive or direct code execution vector in most scenarios. A successful exploitation resulting in a denial-of-service condition through application crash would require specific heap placement conditions that are difficult to control remotely without additional context. The container-type validation introduced in previous patches addressing CVE-2023-42464 failed to resolve this issue because it only validated the outer array structure and did not inspect or validate each individual element contained within an accepted sl_array_t instance. This oversight highlights a common pattern in complex data parsing logic where structural integrity is checked but payload content validation is neglected, allowing malformed sub-elements to bypass security controls.

From a threat intelligence perspective, this vulnerability aligns with ATT&CK technique T1005, which covers Data from Local System Retrieval, as it enables the extraction of internal system information through networked file services. The absence of confidentiality channels in AFP by default exacerbates the risk, although even encrypted sessions would not prevent the memory read itself, only its interception. Mitigation strategies must prioritize immediate patching to version 4.5.2 or later, where the developers have implemented proper element-level validation within the sl_createCNIDArray function. Administrators should also enforce strict access controls by disabling guest UAMs and restricting Spotlight-enabled volumes to authenticated users with verified credentials until patches are applied. Regular auditing of AFP configurations ensures that unnecessary attack surfaces remain minimized, reducing the likelihood of exploitation even if similar vulnerabilities emerge in future updates.

Responsible

GitHub M

Reservation

10/14/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!