CVE-2024-8765

7.3 HIGH

📋 TL;DR

This vulnerability allows unauthenticated attackers to bypass authentication in lunary-ai/lunary by including '/auth/' in API endpoint paths. Attackers can access sensitive data, modify information, and use other organizations' resources without authorization. All deployments using the affected version are vulnerable.

💻 Affected Systems

Products:
  • lunary-ai/lunary
Versions: git commit afc5df4 and potentially earlier versions
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Any deployment using the vulnerable code path is affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of all organizations' data including sensitive information theft, unauthorized resource consumption, and data manipulation across all tenants.

🟠

Likely Case

Unauthorized access to sensitive organizational data and resource misuse leading to data breaches and financial impact.

🟢

If Mitigated

Limited exposure if network controls restrict access, but authentication bypass remains possible for allowed connections.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires only adding '/auth/' to endpoint paths, making it trivial for attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Commit 7ff89b0304d191534b924cf063f3648206d497fa

Vendor Advisory: https://github.com/lunary-ai/lunary/commit/7ff89b0304d191534b924cf063f3648206d497fa

Restart Required: No

Instructions:

1. Update to commit 7ff89b0304d191534b924cf063f3648206d497fa or later. 2. Deploy the updated code. 3. Verify the fix by testing authentication requirements on endpoints.

🔧 Temporary Workarounds

Network Access Restriction

all

Restrict network access to the lunary application to trusted IPs only

WAF Rule

all

Implement WAF rules to block requests containing '/auth/' in paths to sensitive endpoints

🧯 If You Can't Patch

  • Implement strict network segmentation and firewall rules to limit access to the application
  • Deploy a reverse proxy with authentication requirements for all endpoints

🔍 How to Verify

Check if Vulnerable:

Test if endpoints that should require authentication are accessible when '/auth/' is added to the path

Check Version:

git log --oneline -1

Verify Fix Applied:

Verify that adding '/auth/' to endpoint paths no longer bypasses authentication

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns to endpoints containing '/auth/'
  • Authentication failures followed by successful requests with '/auth/' in path

Network Indicators:

  • HTTP requests to sensitive endpoints with '/auth/' in the URL path from unauthenticated sources

SIEM Query:

source="lunary.logs" AND (url:"/auth/" AND NOT user_authenticated:true)

🔗 References

📤 Share & Export