Countly countly-server
countly-server: Unauthenticated Path Traversal via Public Image and Screenshot Routes Leads to Read Internal Files
countly-server is the server-side part of Countly, a product analytics solution. Prior to 24.05.50 and 25.03.44, public image and screenshot routes implemented in frontend/express/app.js, plugins/star-rating/frontend/app.js, and plugins/dashboards/frontend/app.js concatenate attacker-controlled wildcard paths without containment validation. On deployments using the local filesystem backend, an unauthenticated request can traverse outside the intended asset directories and reach getStats or getStream in api/utils/countlyFs.js, allowing arbitrary readable server files to be disclosed. The affected routes include /appimages/*, /memberimages/*, */screenshots/*, /star-rating/images/*, and /dashboards/images/screenshots/*. This issue is fixed in versions 24.05.50 and 25.03.44.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 24.05.50
- >= 25.03, < 25.03.44
Fixed in 24.05.50, 25.03.44
Mitigation
Upgrade countly-server to 24.05.50 or 25.03.44 or later.
References
- Vendor advisory github.com/Countly/countly-server/security/adv…
- Patch github.com/Countly/countly-server/commit/405cb…
- Patch github.com/Countly/countly-server/commit/8004d…
2 more
- Release notes github.com/Countly/countly-server/releases/tag…
- Release notes github.com/Countly/countly-server/releases/tag…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.