countly-server vulnerabilities

In countly-server, public image and screenshot routes using the local fs storage backend call getStream and pipe filesystem streams to HTTP responses without an error listener. An unauthenticated request containing a URL-encoded dot can make createReadStream open a directory, emit an asynchronous EISDIR error, and terminate the Node.js process as an unhandled exception. Fixed in 24.05.50 and 25.03.44.

In countly-server, the authenticated data-migration deletion route passes the user-controlled exportid to clean_up_data without path validation. The identifier is concatenated into a path resolved outside the intended import directory and removed recursively, allowing an application administrator or user with migration permission to delete writable files or directory trees. Fixed in 24.05.50 and 25.03.44.

In countly-server, public image and screenshot routes 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, allowing arbitrary readable server files to be disclosed. Fixed in 24.05.50 and 25.03.44.