'Not rocket surgery' claims researcher who found six Danfoss fridge controller zero-days in under an hour
A Dutch cybersecurity researcher claims he found six zero-days in Danfoss refrigeration controller firmware in under an hour, then delivered a withering assessment of the vendor's defenses against memory corruption.
- He said that he went looking in random places where strcpy() is invoked, given the vendor's "extremely liberal use" of the function (which doesn't check whether the destination buffer is large enough), and swiftly found five cases in which he said he could trigger a segfault with a one-line cURL command.
- He described the final zero-day as a "trivial" pre-auth memory corruption bug which again starts with a segfault but can be wangled into an RCE "with some additional effort." Meijer also considered whether attackers could maintain access after a reset, as seen with implants such as Saltwater and Firestarter.
- He said the vendor's advice following the attacks on European supermarkets and blood banks in recent weeks – rotating creds, applying patches, enabling strict session control – was insufficient given the flaws in the controllers' codebase.
Danfoss has consistently blanked our requests for information since being implicated in at least some of the attacks that affected European supermarkets recently, alongside rival controller vendors Copeland and Dixell.
- "We recommend against allocating scarce security resources to patching efforts and instead focus on reducing exposure." The CCB likewise urged operators to remove direct internet exposure immediately, but also recommended applying patches when they become available.
- "In such a scenario, an attacker could either retain remote access or leave a time-triggered payload for a 2nd (or 3rd...) strike – increasing damage by spoiling new batches of food," said Meijer.
- The Centre for Cybersecurity Belgium (CCB) warns that the flaws could let attackers take control without credentials, potentially retain access after resets, or disable controllers altogether.
- Meijer added: "Any reasonably experienced exploit developer will agree exploiting straightforward stack-based buffer overflows on ARM Linux without exploit mitigations is very straightforward.
- "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," he wrote.
How this summary was made: extractive summary — built from the sources' own reporting. It is drawn only from the reporting of the sources listed below — read the originals for full detail. How we summarize →