I suspect that it must be the central server that this camera reports to that is infected, either directly, or indirectly with some program sitting at a nearby router listening for traffic.
I suspect that it must be the central server that this camera reports to that is infected, either directly, or indirectly with some program sitting at a nearby router listening for traffic.
If a firmware update exists, its probably too technically challenging for Joe User to find and install. For a lot of these devices, there isn't even a published fix. These manufacturers are just rebranding some generic camera from a larger manufacturer or using the same camera and IoT guts and putting them into different cases. These companies probably don't even have a software developer on staff who has access to these firmwares, just perhaps a binary blob, assuming they have any software people on staff at all.
https://www.pentestpartners.com/blog/hacking-the-aldi-ip-cct...
Also Brian Krebs examined that Foscam camera and found it enabled a P2P protocol and opened a port on the firewall using UPnP as well:
https://krebsonsecurity.com/2016/02/this-is-why-people-fear-...
If you knew about the risk, you would have secured your router firewall. If you did not know, you wouldn't be rushing to install the firmware.
Once the camera is compromised, it can modify the firmware being transmitted (to compromise it) or prevent its install.
I suppose there's a follow-up story to be had on routers that come with UPNP enabled by default, because wherever that's the case, your firewall has a hole poked in it as soon as the device powers up and connects to the LAN.
Usually much less than 5 minutes. There's just that much Internet scanning.
If NAT is configured properly, then there is no risk.