ASUSTOR Community Forum

sandro_rocha wrote:

father.mande wrote:Hi,

for specialist Docker is useful if you create your own container (test new version, create prototype) AND if you assume the permanent update of libraries and scripts inside ...
When you used pre-created container from HUB ... no control is done ... and it's at your OWN risk

Last even a virus check is done ... crypto mining is not a virus ... it's a normal application ... so never identified as a virus ... only the access open (generally a reverse connect) can be (or not) identified.

If you are really interested by container ... use tools where you have all the hand and control (like LXC or direct namespace management) so you keep a very large % of control on what are inside.
or if for you like and want to use Docker (even it's own internal security holes) ... create yourself container ... it's describe as difficult (for selling services) when in reality it's easy if you have a minimum of Linux administration skills (some free student formations exist on the Web)

So best solution is TRASH the bad container and all dependencies (some containers works with others containers started hidden), and search for another HUB and verify that it's not the same with another name

Philippe.
NB I am a user so you can trash this advice, but I have used Docker, LXC and Namespace on multiples NAS (and write some tool-book for another NAS brand) ... and today I build my own isolated environment like myHD APKG (an isolated Ubuntu 18.04 env.) or use LXC

I installed Docker-CE and didn't do anything else, didn't download or install any images, didn't start any containers and, a few hours later, there were four containers running. What explains that? Either the version available for the AS1002T is compromised or there is a security breach that allows external control.

cheehoong wrote:

sandro_rocha wrote:

father.mande wrote:Hi,

for specialist Docker is useful if you create your own container (test new version, create prototype) AND if you assume the permanent update of libraries and scripts inside ...
When you used pre-created container from HUB ... no control is done ... and it's at your OWN risk

Last even a virus check is done ... crypto mining is not a virus ... it's a normal application ... so never identified as a virus ... only the access open (generally a reverse connect) can be (or not) identified.

If you are really interested by container ... use tools where you have all the hand and control (like LXC or direct namespace management) so you keep a very large % of control on what are inside.
or if for you like and want to use Docker (even it's own internal security holes) ... create yourself container ... it's describe as difficult (for selling services) when in reality it's easy if you have a minimum of Linux administration skills (some free student formations exist on the Web)

So best solution is TRASH the bad container and all dependencies (some containers works with others containers started hidden), and search for another HUB and verify that it's not the same with another name

Philippe.
NB I am a user so you can trash this advice, but I have used Docker, LXC and Namespace on multiples NAS (and write some tool-book for another NAS brand) ... and today I build my own isolated environment like myHD APKG (an isolated Ubuntu 18.04 env.) or use LXC

I installed Docker-CE and didn't do anything else, didn't download or install any images, didn't start any containers and, a few hours later, there were four containers running. What explains that? Either the version available for the AS1002T is compromised or there is a security breach that allows external control.

I did some test too. If you DMZ your router to your Asustor, is high chance you will get this issue. Which I did before.
Now I hide it at the back ot router, limit the port open, then I did get issue with docker being injected with the mining "virus"
guess the asustor docker is open to attach, security is not good enough.

father.mande wrote:Hi,

I can't help you on docker ... but just for your information

backdoor or mining (in docker) use only output connection ... so closing port is not enough
... lot of them use tools like Ngrok (I use it ) or equivalent ... this tools is a getaway in Internet (like ez-connect used by Asustor)
... NAS do a connection to the server ... the client do a connection to the server (gateway) and a tunnel is created to localhost on NAS ... so after you can do what you want and enter in the NAS (or any server) easily

So they used ONLY output connection, they can hide client under any name, because it's statically linked (no dynamic library) ...

The only way (to verify if it is or not your case) is to do a survey of output connection and limit it, if iptables in NAS have the tables and rules present to do that.

It's one (not the only) reason that I disapprove of any usage of Docker (except if you do it yourself) ... but each can have a different advice ...

Philippe.

sandro_rocha wrote: I know it's a stupid question, but how do I survey outgoing connections? And if so, how do I use iptables (if it exists on the NAS) to limit them?
ps: I have an Ez-Connect account, although I never used it to access the NAS. I usually use No-IP (DDNS). I travel a lot and I need access to the NAS when I'm away from home.
ps2: I also don't like the docker very much. But it is that or not to have applications, since Asustor does not provide native versions of them.