09/29/2026
What do you do when the device you're attacking refuses to talk back?
Synack Red Team researcher Shea Norwood found an unauthenticated command injection bug in a Nortek Linear eMerge E3, the appliance behind badge readers, door locks, and the credential database for facilities. The endpoint would run any command handed to it. It just never said so. No error, no output, no visible change.
So Shea made it talk in a language it couldn't help but speak.
A sleep 5 payload delayed the response by five seconds. Double the sleep, double the delay. Then came the real test: smuggling command output out as a DNS lookup, caught on a Burp Collaborator listener the appliance never knew existed. The HTTP response gave up nothing. The DNS traffic gave up everything, including the exact user the shell was running as.
Full compromise of a door controller isn't just a shell. It's physical access, employee records, and compliance exposure riding on one unsanitized parameter.
Blind doesn't mean unexploitable. Read how timing and DNS turned a silent endpoint into full remote code ex*****on 👇
https://hubs.ly/Q04yBNcP0