CVE-2026-129123 in C-Kermit
Summary
by MITRE • 11/13/2026
C-Kermit 8.0.200 before 11.1.515 contains a buffer overflow vulnerability in getreply() in ckcftp.c that allows malicious FTP servers to overwrite client memory by sending overlong security replies. Attackers controlling or intercepting an FTP server can send long PBSZ replies after AUTH TLS, or long ADAT replies in GSSAPI, Kerberos 4, and SRP builds, overflowing the static reply_buf with attacker-controlled bytes.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/13/2026
The vulnerability identified in C-Kermit versions prior to 11.1.515 represents a critical buffer overflow flaw located within the getreply function of the ckcftp.c source file. This defect arises from insufficient validation of input data received during FTP session negotiations, specifically concerning security-related commands and responses. The core technical issue is that the application utilizes a static reply_buf to store incoming server replies without performing adequate bounds checking before copying the data into this fixed-size buffer. When an attacker controls or intercepts the communication channel with an FTP server, they can craft maliciously oversized response packets designed to exceed the capacity of this internal buffer.
The exploitation vector primarily targets two specific scenarios within the FTP protocol's security negotiation phase. In the first scenario involving AUTH TLS commands, a compromised or rogue FTP server can respond with a PBSZ (Protection Buffer Size) command reply that contains an excessively long string of data. Similarly, in environments utilizing GSSAPI, Kerberos 4, or SRP authentication mechanisms, the attacker can send malformed ADAT (Authentication Data) replies containing more bytes than the buffer can accommodate. These overlong security replies trigger a classic stack-based buffer overflow condition where the excess attacker-controlled bytes spill beyond the allocated memory space of reply_buf into adjacent memory regions.
This memory corruption allows for severe operational impacts ranging from denial of service to arbitrary code execution. By carefully crafting the payload, an attacker can overwrite critical program data such as return addresses or function pointers stored on the stack. This manipulation enables the redirection of program flow to malicious shellcode injected by the attacker, effectively granting them remote code execution capabilities on the client machine running C-Kermit. The vulnerability is particularly dangerous because it requires no user interaction beyond initiating an FTP connection to a hostile server, making it suitable for automated attacks or man-in-the-middle scenarios where network traffic can be intercepted and modified.
From a classification perspective, this flaw aligns with CWE-120 Buffer Copy without Checking Size of Input which describes the failure to verify that input data fits within the destination buffer before copying. Additionally, the exploitation technique maps to MITRE ATT&CK Tactic TA0004 Privilege Escalation and specifically Technique T1068 Exploitation for Privilege Escalation if the overflow leads to gaining higher system privileges, or generally falls under remote code execution patterns associated with network service vulnerabilities. The lack of input sanitization in handling protocol-specific security replies highlights a fundamental gap in secure coding practices regarding buffer management during external data ingestion.
Mitigation strategies must prioritize immediate software updates as the primary defense vector. Users and administrators should upgrade C-Kermit to version 11.1.515 or later where this boundary check has been implemented within the getreply function to prevent memory overwrites. In environments where upgrading is not immediately feasible, network segmentation can provide a layer of protection by restricting FTP client access to only trusted and verified servers. Furthermore, deploying intrusion detection systems capable of identifying anomalous packet sizes during FTP negotiation phases may help in detecting attempted exploitation activities before they result in successful compromise. Regular security audits focusing on buffer handling in legacy or specialized communication tools are essential to prevent similar vulnerabilities from persisting in critical infrastructure components.