"CasaOS is an open-source Personal Cloud system.
Due to a lack of IP address verification, unauthenticated attackers can execute arbitrary commands as root on CasaOS instances.
The problem was addressed by improving the detection of client IP addresses in 391dd7f. This patch is part of CasaOS 0.4.4.
Users should upgrade to CasaOS 0.4.4. If they can't, they should temporarily restrict access to CasaOS to untrusted users, for instance by not exposing it publicly."
-nvd.nist.gov
API endpoints of casaos before 0.4.4, /v1/folder?path= and /v1/file?path= can be bypassed just by editing the X-Forwarded-For header with the loopback address in a get request,
this easy XFF bypass can allow us to see OS systems files with full path which may contain sensitive information.
[*] burp_proof.png
Looking for vulnerable targets
Some tweets are saying you can find vulnerable versions just with this FOFA query: body="/CasaOS-UI/public/index.html"
But to be honest this query is not so accurate, because it will give back all casaos istances mapped by FOFA.
Going deeper, I found that almost all vulnerable hosts have the same "fid" (FOFA ID), fid="mHDuCDefQ9WP96AEzB5JMQ=="
As we can see (during the publication of this article) more than 2000 hosts are vulnerable to this.
Fortunately, vulnerable hosts are decreasing thanks to people's awareness to update their software.
[*] fofa_casaos.png