countly-server is the server-side part of Countly, a product analytics solution

Why it is Yellow

• CVSS 7.5 high
• Remotely exploitable without logging in

References

• https://github.com/Countly/countly-server/commit/72f19bc5161117fa02a224bf9f7316bf42dae58d
• https://github.com/Countly/countly-server/commit/f9ad31480f94ee3ccc0f12708c8804be9c803f95
• https://github.com/Countly/countly-server/releases/tag/24.05.50
• https://github.com/Countly/countly-server/releases/tag/25.03.44
• https://github.com/Countly/countly-server/security/advisories/GHSA-86cv-qwp9-jwp3
• https://github.com/Countly/countly-server/security/advisories/GHSA-86cv-qwp9-jwp3

Original description

countly-server is the server-side part of Countly, a product analytics solution. Prior to 24.05.50 and 25.03.44, star-rating/images/ and dashboards/images/screenshots/ are among public image and screenshot routes using the local fs storage backend that 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, allowing repeated requests to keep the analytics API unavailable. The affected routes also include /appimages/*, /memberimages/*, and */screenshots/*. This issue is fixed in versions 24.05.50 and 25.03.44.