CVE-2024-8999: CWE-862 Missing Authorization in lunary-ai lunary-ai/lunary
lunary-ai/lunary version v1.4.25 contains an improper access control vulnerability in the POST /api/v1/data-warehouse/bigquery endpoint. This vulnerability allows any user to export the entire database data by creating a stream to Google BigQuery without proper authentication or authorization. The issue is fixed in version 1.4.26.
AI Analysis
Technical Summary
CVE-2024-8999 is an improper access control vulnerability (CWE-862) identified in lunary-ai/lunary version v1.4.25. The vulnerability exists in the POST /api/v1/data-warehouse/bigquery endpoint, which is designed to export data streams to Google BigQuery. Due to missing authorization checks, any unauthenticated user can invoke this endpoint to export the entire database contents without restriction. This means an attacker can exfiltrate sensitive data at will, compromising confidentiality. Additionally, the lack of integrity and availability controls means attackers could potentially disrupt or manipulate data exports. The vulnerability is remotely exploitable over the network without any privileges or user interaction, contributing to its high CVSS score of 9.8. The issue was publicly disclosed on March 20, 2025, and fixed in lunary-ai/lunary version 1.4.26. No public exploits have been reported yet, but the critical nature of the flaw demands immediate attention. The vulnerability affects all deployments running the vulnerable version, especially those exposing the API endpoint to untrusted networks.
Potential Impact
For European organizations, this vulnerability poses a severe risk of data breach and loss of data integrity. Organizations using lunary-ai/lunary for data warehousing and analytics could suffer significant exposure of sensitive business, customer, or personal data if exploited. This could lead to regulatory penalties under GDPR due to unauthorized data disclosure. The ability to export entire databases without authentication also risks intellectual property theft and competitive disadvantage. Furthermore, attackers could disrupt normal data operations by manipulating or deleting data streams, impacting business continuity. The critical severity and ease of exploitation mean that any exposed lunary-ai/lunary instance is a high-value target for attackers, including cybercriminals and state-sponsored actors. The reputational damage and financial losses from such a breach could be substantial.
Mitigation Recommendations
1. Immediately upgrade all lunary-ai/lunary deployments to version 1.4.26 or later, where the vulnerability is fixed. 2. Restrict network access to the /api/v1/data-warehouse/bigquery endpoint using firewalls or API gateways to allow only trusted internal systems. 3. Implement strong authentication and authorization controls on all API endpoints, especially those handling sensitive data exports. 4. Monitor logs and network traffic for unusual or unauthorized BigQuery export attempts. 5. Conduct a thorough audit of data access and export activities to detect any prior exploitation. 6. Employ data loss prevention (DLP) solutions to detect and block unauthorized data exfiltration. 7. Educate development and operations teams about secure API design and the importance of access control. 8. If immediate patching is not possible, consider temporarily disabling the vulnerable endpoint or isolating the affected systems from untrusted networks.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Denmark, Belgium
CVE-2024-8999: CWE-862 Missing Authorization in lunary-ai lunary-ai/lunary
Description
lunary-ai/lunary version v1.4.25 contains an improper access control vulnerability in the POST /api/v1/data-warehouse/bigquery endpoint. This vulnerability allows any user to export the entire database data by creating a stream to Google BigQuery without proper authentication or authorization. The issue is fixed in version 1.4.26.
AI-Powered Analysis
Technical Analysis
CVE-2024-8999 is an improper access control vulnerability (CWE-862) identified in lunary-ai/lunary version v1.4.25. The vulnerability exists in the POST /api/v1/data-warehouse/bigquery endpoint, which is designed to export data streams to Google BigQuery. Due to missing authorization checks, any unauthenticated user can invoke this endpoint to export the entire database contents without restriction. This means an attacker can exfiltrate sensitive data at will, compromising confidentiality. Additionally, the lack of integrity and availability controls means attackers could potentially disrupt or manipulate data exports. The vulnerability is remotely exploitable over the network without any privileges or user interaction, contributing to its high CVSS score of 9.8. The issue was publicly disclosed on March 20, 2025, and fixed in lunary-ai/lunary version 1.4.26. No public exploits have been reported yet, but the critical nature of the flaw demands immediate attention. The vulnerability affects all deployments running the vulnerable version, especially those exposing the API endpoint to untrusted networks.
Potential Impact
For European organizations, this vulnerability poses a severe risk of data breach and loss of data integrity. Organizations using lunary-ai/lunary for data warehousing and analytics could suffer significant exposure of sensitive business, customer, or personal data if exploited. This could lead to regulatory penalties under GDPR due to unauthorized data disclosure. The ability to export entire databases without authentication also risks intellectual property theft and competitive disadvantage. Furthermore, attackers could disrupt normal data operations by manipulating or deleting data streams, impacting business continuity. The critical severity and ease of exploitation mean that any exposed lunary-ai/lunary instance is a high-value target for attackers, including cybercriminals and state-sponsored actors. The reputational damage and financial losses from such a breach could be substantial.
Mitigation Recommendations
1. Immediately upgrade all lunary-ai/lunary deployments to version 1.4.26 or later, where the vulnerability is fixed. 2. Restrict network access to the /api/v1/data-warehouse/bigquery endpoint using firewalls or API gateways to allow only trusted internal systems. 3. Implement strong authentication and authorization controls on all API endpoints, especially those handling sensitive data exports. 4. Monitor logs and network traffic for unusual or unauthorized BigQuery export attempts. 5. Conduct a thorough audit of data access and export activities to detect any prior exploitation. 6. Employ data loss prevention (DLP) solutions to detect and block unauthorized data exfiltration. 7. Educate development and operations teams about secure API design and the importance of access control. 8. If immediate patching is not possible, consider temporarily disabling the vulnerable endpoint or isolating the affected systems from untrusted networks.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- @huntr_ai
- Date Reserved
- 2024-09-19T14:18:48.818Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 68ef9b2e178f764e1f470e99
Added to database: 10/15/2025, 1:01:34 PM
Last enriched: 10/15/2025, 1:08:43 PM
Last updated: 10/16/2025, 8:49:25 AM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-0277: CWE-693 Protection Mechanism Failure in HCL Software BigFix Mobile
MediumCVE-2025-54539: CWE-502 Deserialization of Untrusted Data in Apache Software Foundation Apache ActiveMQ NMS AMQP Client
HighCVE-2025-0276: CWE-693 Protection Mechanism Failure in HCL Software BigFix Modern Client Management
MediumCVE-2024-0400: CWE-94 Improper Control of Generation of Code ('Code Injection') in Hitachi Energy MACH SCM
HighCVE-2025-55090: CWE-125 Out-of-bounds Read in Eclipse Foundation NetX Duo
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.