[Warning] RCE in xalpha v0.11.4 ~ v0.11.8 about xalpha HOT 4 CLOSED

Thanks for the thorough report. The quickest fix is to first check the code format when initiating fundinfo? i.e., it has to be six digits instead of a url str. If this protection is implemented, do you see any potential risk left?

Besides, can you see any scenario that the current issue can have realistic security issues? Because to me, the fundinfo code is written by the users themselves.

from xalpha.

Ah, i think i see your point now. The scenario could be someone who host a website using xalpha as backend, then when the use input some weird fund code, the backend server can run something very bad if the server has no check on the user's input more than bare xalpha. In this case, the loophole can be used to weaken the server (say a fund summary website backend by xalpha, if any)

from xalpha.

Actually you could just check the code format when initiating fundinfo, you can simply avoid this vulnerability in this way. But I suggest you replace eval() with safer functions to prevent vulnerabilities that may occur in the future.

yeah, if someone host a website using xalpha as backend, The attackers could use the above methods to directly obtain server permissions (attackers could use functions such as os.system() to execute cmd and directly obtain the cmd shell.)

from xalpha.

shall be fixed in 0.11.9

from xalpha.