Six Unpatched Danfoss Refrigeration Controller Flaws Allow Remote Root — and the Newest Firmware Doesn't Fix Them
Six Unpatched Danfoss Refrigeration Controller Flaws Allow Remote Root — and the Newest Firmware Doesn't Fix Them
The fridges are under attack again, and this time there is no patch coming. Dutch security consultancy Midnight Blue disclosed this week that six vulnerabilities in the Danfoss AK-SM800A refrigeration controller — the box that runs a store's fridges and freezers and lets maintenance firms manage it remotely — could let a remote attacker take over a controller without logging in. No CVE identifiers have been assigned yet, the vendor's advisory page lists no fix, and the researchers' most striking finding: the newest firmware, version 5.4.0 (dated November), does not fix the flaws. "It's not really possible either," the researchers told trade publication Cooling Post, "because according to the file timestamp this firmware was likely built on October 29, before the second wave of cyber attacks and well before our vulnerability reports."
Researcher Carlo Meijer found the six flaws in less than an hour of manual review of firmware version 5.3.2 — every version up to and including it is affected. Five of the flaws sit in web request handlers that require no login, inside a program that runs as root; through one of them the researchers demonstrated arbitrary code execution as root on older firmware and confirmed the same bugs in 5.3.2. The sixth lives in the gateway that enforces the controller's "Strict mode" — Danfoss's login-protection layer that requires encrypted connections and session tokens. When the researchers ran 5.3.2 in an emulator with Strict mode on, that flaw crashed the gateway, and they say the crash could be converted into code execution with more work; the gateway lacks stack canaries and other basic exploit defenses. With root code running, an attacker can change setpoints, start defrost cycles, hide the activity from logs, and — because the controllers lack secure boot — plant code that survives factory reset and firmware updates.
The context is what turns a firmware audit into an urgent operational warning. AK-SM800A-class controllers were targeted in the attacks that triggered unwanted defrost cycles and destroyed stock in French stores starting October 11, and in a second wave across Europe that began last week. Germany's BSI, which issued a security notice and has documented earlier tampering incidents with the AK-SM800A in several countries, says it has no information tying the six new flaws to those attacks — and notably corrected its own statement to say it cannot rule out that 5.4.0 is affected. But the agencies' conclusion is blunt: updating firmware, changing default passwords and turning on Strict mode is not enough on its own for any controller left reachable from the internet — because Strict mode's own gateway is one of the vulnerable components. Belgium's CCB, Ireland's NCSC and Germany's BSI all told operators the same thing this week: take the management interfaces off the internet now.
What Should You Do?
- Remove internet exposure for every AK-SM800A — including reachability through 4G/5G modems. Danfoss's own update guide says the controller should not be directly reachable from the public internet, and the agencies say this must not wait for a patch.
- Route remote access through a secure VPN or protected internal network. A firewall rule allowing only your service company's IP addresses is a short-term measure at best.
- Audit for tampering: check temperature setpoints, defrost schedules, alarm settings, user accounts and remote-access settings for changes you did not make. If you suspect compromise, change all credentials and verify the connected refrigeration equipment works properly.
- Keep monitoring alive safely. Before cutting the data feed to your refrigeration service company, check contract and insurance terms, and set up protected remote access so monitoring can continue — an offline controller in a food retail chain has its own failure costs.
The WAF Angle
A refrigeration controller is an edge IoT web server in everything but name: a root-running web stack, unauthenticated request handlers, and a hardened perimeter layer that turns out to be vulnerable itself. The Strict mode finding is the lesson web defenders should internalize — a security control bolted onto an untrusted attack surface becomes part of that surface, the same pattern we flagged when a hardened Windows logging subsystem became the exploit path in SignDrop and when attackers turned hardened firewalls against their owners in the Apache HTTP/2 emergency's appliance cousins. For OT assets like this, the only durable architecture is network isolation: if a device must be remote-managed, it gets a VPN tunnel and an allow-listed path — never a public IP that a WAF in front of it would merely be guarding a door the device shouldn't have opened at all.