CVE-2026-62319 in Netatalkinfo

Summary

by MITRE • 11/20/2026

Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 1.5.0 until 4.5.1, dsi_stream_receive in libatalk/dsi/dsi_stream.c independently clamps dsi_doff and dsi_len for DSIWrite requests without enforcing that the data offset is no greater than the declared frame length. An authenticated AFP client can send dsi_doff greater than dsi_len, causing the receiver to consume bytes from a queued subsequent frame before libatalk/dsi/dsi_write.c detects the inconsistency. The irreversible stream desynchronization lets the attacker control the next parsed DSI header and payload and corrupts protocol framing for the connection. This issue is fixed in version 4.5.1.

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 compatible with Apple Filing Protocol clients. The vulnerability identified within versions ranging from 1.5.0 through 4.5.1 resides in the DSI stream reception logic located in libatalk/dsi/dsi_stream.c. This component is responsible for parsing incoming Data Stream Interface frames, which form the foundational transport mechanism of the AFP protocol. During normal operation, the system processes requests by validating various fields within the frame header to ensure integrity and correct sequencing. However, a specific logical flaw exists regarding how the data offset field, referred to as dsi_doff, is handled relative to the declared length field, known as dsi_len.

The core technical deficiency lies in an independent clamping operation that fails to enforce a critical consistency check between these two fields. Specifically, when processing DSIWrite requests, the code applies bounds checking to both values individually but does not verify that the data offset is less than or equal to the total frame length. This oversight creates a scenario where an authenticated AFP client can craft a maliciously structured request with a dsi_doff value that exceeds the declared dsi_len. Under standard protocol expectations, such a mismatch should immediately terminate the connection or reject the packet as malformed. Instead, due to the lack of cross-field validation, the receiver proceeds to process the frame using the inflated offset value.

This logical error triggers an irreversible stream desynchronization event with severe operational consequences. By specifying an offset greater than the current payload length, the attacker forces the parser to consume bytes from a subsequent queued frame as if they were part of the current request's data segment. This action effectively shifts the parsing window forward by an arbitrary amount determined by the attacker. Consequently, when libatalk/dsi/dsi_write.c eventually detects the inconsistency or attempts to parse the next expected DSI header, it is operating on corrupted state information. The protocol framing for the entire connection becomes compromised because the parser's internal pointers are no longer aligned with the actual byte stream structure sent by the client.

The impact of this desynchronization extends beyond simple data corruption. Because the attacker controls how many bytes are skipped from subsequent frames, they can manipulate which parts of future packets are interpreted as headers versus payloads. This capability allows for precise control over the next parsed DSI header and payload content. In practical terms, an adversary could potentially bypass authentication checks by manipulating frame boundaries to skip critical validation steps or inject malicious commands into the protocol stream that would otherwise be rejected due to structural invalidity. The ability to corrupt protocol framing effectively undermines the integrity of the entire AFP session, allowing for potential remote code execution or unauthorized access depending on how subsequent frames are processed and interpreted by vulnerable services.

From a classification perspective, this vulnerability aligns with CWE-20 Improper Input Validation, as the system fails to adequately validate input data against expected structural constraints. Furthermore, it relates to CWE-367 Time-of-check Time-of-use Race Condition concepts in terms of state consistency, although more accurately described under CWE-194 Unexpected Sign Extension or similar logic errors involving buffer offset miscalculations. In the context of the MITRE ATT&CK framework, this flaw facilitates lateral movement and privilege escalation by allowing an authenticated attacker to manipulate protocol states, potentially leading to unauthorized access (T1078) or exploitation of application vulnerabilities through malformed input (T1190).

Mitigation strategies primarily involve upgrading Netatalk to version 4.5.1 or later, where the developers have implemented proper validation logic to ensure that dsi_doff does not exceed dsi_len before processing begins. For environments unable to upgrade immediately, network-level controls such as strict firewall rules limiting AFP traffic to trusted subnets can reduce exposure. Additionally, implementing deep packet inspection at the network perimeter may help detect anomalous frame structures characterized by offset-to-length mismatches typical of this exploitation vector. Regular auditing of file server configurations and ensuring that only necessary ports are exposed further reduces the attack surface associated with legacy protocol implementations like AFP.

Responsible

GitHub M

Reservation

07/13/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00591

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!