Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-8763: CWE-1333 Inefficient Regular Expression Complexity in lunary-ai lunary-ai/lunary

0
High
VulnerabilityCVE-2024-8763cvecve-2024-8763cwe-1333
Published: Thu Mar 20 2025 (03/20/2025, 10:08:56 UTC)
Source: CVE Database V5
Vendor/Project: lunary-ai
Product: lunary-ai/lunary

Description

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the lunary-ai/lunary repository, specifically in the compileTextTemplate function. The affected version is git be54057. An attacker can exploit this vulnerability by manipulating the regular expression /{{(.*?)}}/g, causing the server to hang indefinitely and become unresponsive to any requests. This is due to the regular expression's susceptibility to second-degree polynomial time complexity, which can be triggered by a large number of braces in the input.

AI-Powered Analysis

AILast updated: 10/15/2025, 13:19:10 UTC

Technical Analysis

CVE-2024-8763 is a Regular Expression Denial of Service (ReDoS) vulnerability identified in the lunary-ai/lunary repository, specifically within the compileTextTemplate function. The vulnerability stems from the use of the regular expression /{{(.*?)}}/g, which is susceptible to catastrophic backtracking due to its inefficient pattern design. When an attacker submits input containing a large number of braces, the regex engine's processing time grows polynomially, causing the server to hang and become unresponsive. This effectively results in a denial of service condition. The vulnerability does not require any authentication or user interaction, making it remotely exploitable over the network. The affected versions are unspecified, but the vulnerability was identified in the git commit be54057. The CVSS v3.0 score is 7.5, reflecting a high severity due to the ease of exploitation and the impact on availability. No patches or fixes have been linked yet, and no known exploits have been observed in the wild. The root cause is the inefficient regular expression pattern that can be optimized or replaced to prevent excessive backtracking. This vulnerability highlights the risks of using complex regex patterns without proper safeguards in input processing functions.

Potential Impact

For European organizations using lunary-ai/lunary, this vulnerability poses a significant risk of denial of service attacks that can disrupt critical services relying on this software. The server hang caused by the ReDoS attack can lead to downtime, degraded performance, and potential loss of availability for end users. This can affect business continuity, especially for organizations that integrate lunary-ai/lunary into customer-facing applications or internal automation tools. The lack of authentication requirement means attackers can exploit this remotely, increasing the attack surface. Additionally, prolonged service outages may lead to reputational damage and potential regulatory scrutiny under European data protection laws if service availability impacts user data processing. The vulnerability does not directly compromise confidentiality or integrity but severely impacts availability, which is critical for operational resilience.

Mitigation Recommendations

To mitigate CVE-2024-8763, organizations should implement several specific measures: 1) Apply input validation to restrict or sanitize inputs containing excessive braces or suspicious patterns before they reach the vulnerable regex processing function. 2) Limit the size and complexity of user inputs to reduce the risk of triggering catastrophic backtracking. 3) Monitor application logs and performance metrics for signs of hanging or slow response times indicative of ReDoS attempts. 4) If possible, replace the vulnerable regular expression with a more efficient pattern or use alternative parsing methods that do not rely on regex prone to backtracking. 5) Stay alert for official patches or updates from lunary-ai and apply them promptly once available. 6) Employ web application firewalls (WAFs) or rate limiting to detect and block suspicious input patterns targeting this vulnerability. 7) Conduct code reviews and static analysis focusing on regex usage to proactively identify similar risks in other parts of the codebase.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
@huntr_ai
Date Reserved
2024-09-12T20:10:57.346Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 68ef9b2d178f764e1f470e66

Added to database: 10/15/2025, 1:01:33 PM

Last enriched: 10/15/2025, 1:19:10 PM

Last updated: 10/15/2025, 8:13:52 PM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats