CVE-2024-45189
📋 TL;DR
Mage AI has a path traversal vulnerability in its Git Content request that allows remote users with the 'Viewer' role to read arbitrary files from the server. This affects Mage AI deployments where untrusted users have Viewer access. The vulnerability enables unauthorized file disclosure without requiring administrative privileges.
💻 Affected Systems
- Mage AI
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Attackers could read sensitive files like configuration files, API keys, database credentials, and source code, potentially leading to full system compromise.
Likely Case
Unauthorized access to sensitive configuration files and source code, enabling further attacks or intellectual property theft.
If Mitigated
Limited impact if proper access controls restrict Viewer roles to trusted users only.
🎯 Exploit Status
Exploitation requires Viewer role credentials; the vulnerability is publicly documented with proof-of-concept details available.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Check Mage AI releases after vulnerability disclosure
Vendor Advisory: https://research.jfrog.com/vulnerabilities/mage-ai-git-content-request-remote-arbitrary-file-leak-jfsa-2024-001039604/
Restart Required: Yes
Instructions:
1. Update Mage AI to the latest patched version
2. Restart the Mage AI service
3. Verify the fix by testing the Git Content endpoint
🔧 Temporary Workarounds
Restrict Viewer Role Access
allLimit Viewer role assignments to trusted users only and implement network-level access controls.
Network Segmentation
allIsolate Mage AI instances from sensitive systems and implement firewall rules to restrict access.
🧯 If You Can't Patch
- Implement strict access controls for Viewer roles and monitor for suspicious file access patterns.
- Deploy web application firewall (WAF) rules to block path traversal attempts.
🔍 How to Verify
Check if Vulnerable:
Test if a user with Viewer role can access files outside the intended directory via the Git Content endpoint.Check Version:
Check Mage AI version in the application interface or deployment configuration.Verify Fix Applied:
After patching, verify that path traversal attempts via the Git Content endpoint are properly blocked.📡 Detection & Monitoring
Log Indicators:
- Unusual file access patterns in Mage AI logs
- Multiple failed path traversal attempts
Network Indicators:
- HTTP requests to Git Content endpoint with directory traversal sequences (../)
SIEM Query:
source="mage-ai" AND (uri="*../*" OR status=403)