For this particular attack (assuming c2 server compromise?) that might not matter, but ultimately there is a massive difference in attack surface when comparing “direct” with “NATed”
How much would you bet against that being an unauthenticated call or one with leaked hard coded reds?
Assume some javascript that loops through:
http://192.168.0.1/cgi-bin/factoryRestore.sh
http://192.168.0.2/cgi-bin/factoryRestore.sh
http://192.168.0.3/cgi-bin/factoryRestore.sh
up to
http://192.168.0.254/cgi-bin/factoryRestore.sh
Those just give connection errors for me, but:
http://192.168.1.1/cgi/ACT_FACTORY_RESET
gives me a 403 Forbidden error, and if there was a known default password to my router - it'd try and do a factory reset on it. (It actually wouldn't, it'd send back a confirmation popup, but...)
Or are you assuming the user's browser itself is compromised and is running random javascript hitting the NAS address? That would be unfortunate, but I'm not sure I'd blame it on the "6 years past EOL consumer linux device"
Classic old cross origin request forgery. It ranks #7 I owasp’s top 10 website security flaws, and they have this to say about it:
“XSS is the second most prevalent issue in the OWASP Top 10, and is found in around two thirds of all applications.“