Skip to main content
Emerging Threats

Danfoss Fridge Controllers Exposed to Six Zero-Days

Industrial refrigeration control panel with Danfoss-style controller and machinery in a cold storage room.

"Of course, remotely triggering a crash is bad in itself, but being able to leverage the buffer overflow to obtain remote code execution is much worse," wrote Carlo Meijer after scrutinising Danfoss refrigeration controller firmware.

Six zero-days in under an hour: what Meijer found

Carlo Meijer of cyber consultancy Midnight Blue says he examined the AK-SM800A refrigeration controller firmware, version 5.3.2, manually and found six zero-day vulnerabilities in under an hour. Meijer reported locating five separate memory-corruption cases tied to the C library function strcpy(), each of which he said could be driven to a segfault with a one-line cURL command. He described a sixth flaw in the controller’s "session control" layer — an authentication mechanism added in later firmware — as a "trivial" pre-auth memory corruption bug that likewise begins with a crash and can be turned into remote code execution (RCE) "with some additional effort."

Technical failings: strcpy(), root privileges, and missing mitigations

Meijer criticised Danfoss for the "extremely liberal use" of strcpy(), which does not check destination buffer length and stops copying at a null byte; he observed that overcoming strcpy()’s null-byte limitation is "not exactly rocket surgery." He also wrote that the exploited application runs as root. Beyond the specific bugs, Meijer pointed to the absence of basic exploit mitigations — notably stack canaries and position-independent executables — and argued enabling those protections is a matter of setting compiler flags. "These mechanisms have been staples of memory corruption defenses for decades," he wrote, adding there is "simply no excuse" for a network-facing application updated months ago to lack them.

Persistence, spoiling shipments, and bricking: potential attacker options

Meijer explored how attackers might act after initial compromise. He judged it feasible that an attacker could retain access after resets because the controllers do not use their processor's secure boot features. That opens two troubling avenues, he said: leaving implants or time-triggered payloads to spoil later batches of food, or wiping flash memory or pushing malformed firmware to permanently brick controllers. He explicitly compared the latter to tactics used in the December 2025 attack on the Polish electric grid, and cited implants with names such as Saltwater and Firestarter as examples of persistent, destructive tooling.

Centre for Cybersecurity Belgium and vendor response

The Centre for Cybersecurity Belgium (CCB) warned that the flaws could allow attackers to take control without credentials, maintain access after resets, or disable controllers entirely. The CCB urged operators to immediately remove controllers from direct internet exposure and also recommended applying vendor patches when available. Meijer echoed the removal-of-exposure advice and argued that the vendor’s guidance following recent attacks on European supermarkets and blood banks — rotating credentials, applying patches, enabling strict session control — was insufficient given the code-level vulnerabilities he found. The Register’s requests for comment drew no reply from Danfoss; the vendor "did not reply" to queries and has, according to the source, consistently blanked requests for information since being implicated in attacks that affected European supermarkets recently alongside Copeland and Dixell. Danfoss also did not respond when asked about alleged targeting of its controllers in attacks on US commissary appliances over the summer.

What this means for technologists, asset owners, and regulators

  • Technologists and security teams: Focus immediately on exposure reduction — Meijer and the CCB both prioritised removing direct internet access over piecemeal patching. Where possible, verify whether affected controllers run network-facing applications as root and whether compiler-level mitigations (stack canaries, PIE) are enabled.
  • Asset owners and operators: Treat internet-exposed controllers as high-risk. Meijer warned that rotating credentials and enabling session control are inadequate defenses when the underlying codebase contains multiple pre-auth memory-corruption bugs.
  • Regulators and incident responders: The CCB has issued public warnings; regulators may need to push for rapid notification and coordinated remediation plans, given the potential for disruption to food supply lines and critical services referenced in recent incidents.

Meijer’s hands-on, manual testing and the CCB advisory together paint a narrow but urgent picture: readily exploitable memory-corruption bugs in a widely deployed controller family, an architecture lacking basic mitigations, and an immediate operational recommendation to remove internet exposure. Whether Danfoss will respond publicly or ship firmware builds with the recommended compiler defenses and secure-boot support remains unreported; until then, the CCB and at least one researcher are urging operators to act now rather than wait.

Original reporting at The Register