Filecatalyst Threat Research -

Discovery: The FCP protocol lacks granular rate limiting on control packets. By sending crafted SYNC packets with incremental sequence numbers but no actual data payload, an attacker can force the server to allocate memory buffers for non-existent transfers. Impact: With a single 1 Gbps line, a threat actor can exhaust the server’s file descriptor table, causing legitimate transfers to drop and requiring a hard restart. This is distinct from volumetric DDoS—it’s a protocol-level resource starvation.

They matched. So why was FileCatalyst screaming about a mismatch?

FileCatalyst Threat Research: Securing High-Speed Data Transfers filecatalyst threat research

: Improper neutralization of user-supplied jobID parameters allows for SQL injection.

The attacker was using the massive bandwidth of the FileCatalyst server to exfiltrate stolen data from the observatory's other servers. They were hiding stolen research papers and personnel files inside the header data of the pulsar noise, riding the high-speed connection out of the facility disguised as astronomical data. They were banking on the sheer volume of data—petabytes of noise—to hide their stolen megabytes. Discovery: The FCP protocol lacks granular rate limiting

In today's digital landscape, file transfer and collaboration have become essential components of modern business operations. With the rise of remote work and global teams, organizations are increasingly relying on file transfer solutions to share sensitive information across borders and networks. One popular solution that has gained widespread adoption is FileCatalyst, a fast and reliable file transfer platform used by various industries, including finance, healthcare, and government.

Elias frowned. The destination was his local server. No one else had access. He opened the destination folder and looked at the files. They were proprietary .fcsv files—custom encoding used by the telescope's sensors. filecatalyst threat research

High | CVE Status: CVE-2024-28751 (Disclosed)

"Come on," Elias muttered. He opened the FileCatalyst workflow log. He wasn't a security expert, but he knew enough to read a diagnostic. He assumed a network hiccup had corrupted a packet. He clicked Retry .