Cloudron Forum

Hello @sebastienserre Did you enable IPv6 in the Cloudron dashboard? Does the IPv6 detected in the dashboard match with the IPv6 provided by your hoster?

Happy to help. No /app/data/twenty-front/ holds no user-uploaded content. On my instance it only contains front build artifacts: assets/ (hashed JS bundles), images/, manifest.json, index.html, mockServiceWorker.js, all dated from install day and matching what ships in dist/front.orig. Nothing user-generated. The only dynamic piece is the .env symlink, which already points to /run/twenty-front/.env, not into /app/data.

@dark thanks for your report. I looked into them. For transparency, here is our assessment. All the reported issues require the attacker to already have an admin token / compromised admin password. All the issues below are not reproducible as a (compromised) normal user. Also. the issues were reproduced on the demo instance, which of course has the admin username/password displayed in public. We found the report to be thorough and with clear explanation on how to reproduce the problems. From our side, we ack the bugs and have made the following fixes: Problem: Full SSRF via applinks. This is about adding an internal IPs as an applink. Our analysis: Linking to internal apps is a legitimate feature. An applink is fundamentally a bookmark and there's nothing wrong with pointing it at 192.168.1.50 or an internal app. Applinks REST response only returns label and icon not contents of a site. You can't really infiltrate EC2 metadata etc and neither can you make non GET requests. Our fix: We have added a fix now to block server internal IPs like localhost and docker internal network. Problem: SQL injection via dynamic column names. This is about being able to send arbitrary field names in the REST APIs. Our analysis: Indeed, our query builders, should only use field names which are in the db and are part of an allow list. Our fix: We have added allow list to all our model code Problem: 2FA/TOTP BYPASS via skipTotpCheck: true Our analysis: I think this is because the demo instance does not allow you to set a TOTP. It doesn't show an error currently when this happens and leads the user to believe an OTP was set. For the demo server, we can't allow users to set a TOTP because it will make it unsuable for others. Our fix: We will show an error like we show in other places. But also, the password login routes have already been removed in Cloudron 10 (which is yet to be released). That route exists as a backward compat for the CLI. Cloudron only supports OIDC device auth for the CLI from Cloudron 10. Problem: Stored XSS via branding footer Our analysis: right. This issue has been present since ages and our demo instance always has someone putting some alert() or some stupid HTML in there periodically... Our fix: We give in to the non-stop reports about this... We use dompurify now. Thanks for the report again. Very clear and solid notes. I also took the chance to update https://www.cloudron.io/security.html and https://www.cloudron.io/.well-known/security.txt

@ekevu123 great report. Fixed in https://git.cloudron.io/platform/box/-/commit/c7b2e4d95e3ca00924d3ad11781303b479d787d8

@james Rocket.Chat update applied, apps are downloaded. Life is good!

@BenjaminJ you have to use something like https://docs.cloudron.io/packages/dolibarr/#manual-utf8mb4-migration to migrate an existing installation .

Thanks for the quick reaction!!

@girish Well, if developers like @luckow essentially maintain their own appstore, I fully agree. With all other community apps, you always risk going down the Yunohost way - a plethora of apps, many if not most unmaintained. Your USP is - inter alia! - that people can rely on well maintained apps. IMHO opinion, the goal should always be to maintain a broad-ranging, well maintained appstore. This is also relevant in a commercial scenario, where individuals/companies have to ascertain risks before implementing Cloudron („are those apps maintained and up-to-date?“).

Vendor: System manufacturer Product: System Product Name Linux: 5.15.0-179-generic Ubuntu: jammy 22.04 Cloudron: 9.2.0 Execution environment: none none Processor: Intel(R) Xeon(R) CPU E3-1225 v6 @ 3.30GHz x 4 RAM: 32807988KB Disk: /dev/nvme0n1p2 697G [OK] Root disk usage is OK (22%) [OK] Memory usage is OK (46%) [OK] Clock is NTP-synchronized [OK] node version is correct [OK] IPv6 is enabled in kernel. Public IPv6 address detected [OK] docker is running [OK] docker version is correct [OK] MySQL is running [OK] netplan is good [OK] DNS is resolving via systemd-resolved [OK] unbound is running [OK] IPv4 HTTPS to api.cloudron.io/api/v1/helper/public_ip [OK] IPv6 HTTPS to api.cloudron.io/api/v1/helper/public_ip [OK] IPv4 HTTPS to auth.docker.io/token [OK] IPv6 HTTPS to auth.docker.io/token [OK] IPv4 HTTPS to acme-v02.api.letsencrypt.org [OK] IPv6 HTTPS to acme-v02.api.letsencrypt.org [OK] nginx is running [OK] dashboard cert is valid [OK] dashboard is reachable via loopback [OK] No pending database migrations [OK] Service 'mysql' is running and healthy [OK] Service 'postgresql' is running and healthy [OK] Service 'mongodb' is running and healthy [OK] Service 'mail' is running and healthy [OK] Service 'graphite' is running and healthy [OK] Service 'sftp' is running and healthy [OK] box v9.2.0 is running [OK] Dashboard is reachable via IPv4 (https://my.rotovegas.nz) [OK] Dashboard is reachable via IPv6 (https://my.rotovegas.nz) [SKIP] Domain expiry check — whois did not return an expiry date for rotovegas.nz ======== Summary ======== PASS: 30 WARN: 0 FAIL: 0 SKIP: 1 Working version : Invoice Ninja 5.13.22

I wonder if they'll enable mobile editing they have (in Browser). Got it already running on a test VPS I'm happy Cloudrom waits until at least the 34.0.1 release. totally agree

@james said: Hello @panda Thanks for sharing these insights. Maybe you can also share the name of the mail relay that is blocking the attachments for other readers? @james Certainly, we were using smtpfa.st when running into the send problem. Emailing out directly from Cloudron worked but Leantime was a no-go. Down the road, smtpfa.st may work with attachments as they build out their full service.

It works! Thank you!

Hi @james, I can confirm that your workaround solved that issue, thanks for your quick reaction, now I will update Collabora in production!

Hello Upstream reported that the issue will be resolved with the next release. https://github.com/ONLYOFFICE/DocumentServer/issues/3686#issuecomment-4631461296

Hello @crush33 Thanks for the details.