CVE-2025-0189
📋 TL;DR
This vulnerability allows attackers to cause denial of service in aimhubio/aim tracking servers by sending oversized websocket messages containing large images. The server becomes unresponsive while processing these messages, blocking legitimate requests. Anyone running aim version 3.25.0 with the tracking server exposed is affected.
💻 Affected Systems
- aimhubio/aim
📦 What is this software?
Aim by Aimstack
⚠️ Risk & Real-World Impact
Worst Case
Complete service outage where the tracking server becomes completely unresponsive, disrupting all monitoring and logging functionality for machine learning experiments.
Likely Case
Intermittent service degradation where legitimate users experience timeouts or slow responses when attackers periodically send large images.
If Mitigated
Minimal impact with proper rate limiting, input validation, and network segmentation in place.
🎯 Exploit Status
Exploitation requires network access to the tracking server and ability to send websocket messages.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version after 3.25.0
Vendor Advisory: https://huntr.com/bounties/e4c9bf41-72cf-4d04-baaf-8f12b5b7926e
Restart Required: No
Instructions:
1. Update aim to latest version using pip: pip install --upgrade aim 2. Verify version is greater than 3.25.0 3. Restart any running aim tracking servers
🔧 Temporary Workarounds
Implement websocket message size limits
allConfigure websocket server to reject messages exceeding a reasonable size threshold
Network segmentation and access controls
allRestrict network access to aim tracking server to trusted sources only
🧯 If You Can't Patch
- Implement rate limiting on websocket connections
- Deploy a reverse proxy with request size limits in front of the tracking server
🔍 How to Verify
Check if Vulnerable:
Check aim version: aim version | grep 3.25.0Check Version:
aim versionVerify Fix Applied:
Check aim version is greater than 3.25.0: aim version📡 Detection & Monitoring
Log Indicators:
- Unusually large websocket message sizes
- Extended processing times for image tracking requests
- Server timeout errors
Network Indicators:
- Large websocket frames to aim tracking server port
- Sudden increase in websocket traffic
SIEM Query:
source="aim-server" AND (message_size>1000000 OR processing_time>10s)