CVE-2026-49389 in Netatalkinfo

Summary

by MITRE • 11/20/2026

Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 2.0.0 until 4.5.0, afp_catsearch in etc/afpd/catsearch.c computes the spec2 pointer for FPCatSearch and FPCatSearchExt from the unvalidated 16-bit spec_len request field without checking it against the remaining input length. An authenticated AFP client can cause the CatSearch handler to read stale bytes beyond the supplied request data. The bytes are used only as internal comparison criteria and are not returned to the client, and testing under standard server quantum settings did not demonstrate a crash or information disclosure. This issue is fixed in version 4.5.0.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/20/2026

Netatalk serves as a critical interoperability layer for Unix-like operating systems, enabling them to function as Apple Filing Protocol servers within heterogeneous network environments. The vulnerability identified in the afp_catsearch component affects versions ranging from 2.0.0 through 4.5.0 and centers on a fundamental input validation failure within the catsearch.c module of the etc/afpd directory. Specifically, the software computes the spec2 pointer for both FPCatSearch and FPCatSearchExt operations by relying directly on an unvalidated sixteen-bit field named spec_len provided in the client request. The core technical flaw lies in the absence of a bounds check that verifies whether this specified length is consistent with the actual remaining input data available in the buffer. This lack of validation allows for a scenario where the pointer arithmetic proceeds without ensuring that the requested span remains within the allocated memory boundaries defined by the incoming packet size.

From an operational perspective, this architectural weakness permits an authenticated AFP client to trigger the CatSearch handler into reading stale bytes located beyond the legitimate boundary of the supplied request data. In practical terms, when a malicious actor constructs a crafted AFP request with an inflated spec_len value, the server processes the command and attempts to access memory locations that were not intended for this specific operation. Although these out-of-bounds reads do not result in immediate service disruption or direct information leakage back to the client under standard server quantum settings, they represent a significant deviation from secure coding practices. The stale bytes are utilized exclusively as internal comparison criteria during the search process and are never transmitted back to the requesting entity, which mitigates the risk of straightforward remote code execution or sensitive data exfiltration in this specific context but does not eliminate the underlying memory safety violation.

The security implications of this flaw align closely with CWE-125, Out-of-bounds Read, as the application accesses memory beyond its intended buffer limits. Furthermore, because exploitation requires an authenticated connection to the AFP service, it falls under the broader category of issues related to insufficient input validation in network-facing services. While current testing indicates that standard server configurations do not exhibit crashes or information disclosure due to this specific bug, such out-of-bounds reads can potentially lead to undefined behavior depending on the memory layout and state at runtime. In more complex scenarios or different configuration settings, accessing stale data could theoretically influence control flow or expose internal application states, making it a latent risk that warrants immediate remediation regardless of observed exploitability in default environments.

To mitigate this vulnerability, organizations running Netatalk must upgrade to version 4.5.0 or later, where the developers have implemented proper validation checks for the spec_len field against the remaining input length before computing pointers. This fix ensures that any request attempting to access data beyond its defined boundaries is rejected rather than processed. Additionally, administrators should enforce strict authentication policies and limit AFP service exposure to trusted networks only, reducing the attack surface available to potential adversaries. Regular patch management cycles are essential for maintaining the integrity of file server infrastructure, particularly when dealing with open-source suites that may contain legacy code paths susceptible to such memory safety errors.

Responsible

GitHub M

Reservation

05/29/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00460

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!