CVE-2025-32779: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in labsai EDDI
E.D.D.I (Enhanced Dialog Driven Interface) is a middleware to connect and manage LLM API bots. In versions before 5.5.0, an attacker with access to the `/backup/import` API endpoint can write arbitrary files to locations outside the intended extraction directory due to a Zip Slip vulnerability. Although the application runs as a non-root user (`185`), limiting direct impact on system-level files, this vulnerability can still be exploited to overwrite application files (e.g., JAR libraries) owned by the application user. This overwrite can potentially lead to Remote Code Execution (RCE) within the application's context. This issue has been patched in version 5.5.0.
AI Analysis
Technical Summary
CVE-2025-32779 is a path traversal vulnerability classified under CWE-22, affecting the labsai EDDI (Enhanced Dialog Driven Interface) middleware, which is used to connect and manage large language model (LLM) API bots. Specifically, versions of EDDI prior to 5.5.0 contain a Zip Slip vulnerability in the `/backup/import` API endpoint. This vulnerability allows an attacker with access to this endpoint to write arbitrary files outside the intended extraction directory by manipulating the paths within a crafted ZIP archive. Although the application runs under a non-root user (UID 185), which limits the ability to overwrite critical system files, the attacker can overwrite application files owned by this user, such as JAR libraries. Overwriting these files can lead to remote code execution (RCE) within the context of the application, potentially allowing an attacker to execute arbitrary code, manipulate application behavior, or escalate privileges within the application environment. The vulnerability has been addressed in version 5.5.0 of EDDI, and no known exploits are currently reported in the wild. The issue arises from improper validation and sanitization of file paths during ZIP extraction, enabling directory traversal beyond the designated extraction folder.
Potential Impact
For European organizations using labsai EDDI middleware versions prior to 5.5.0, this vulnerability poses a significant risk. Successful exploitation could lead to unauthorized code execution within the application context, potentially compromising the integrity and availability of services relying on EDDI for LLM API bot management. This could disrupt automated workflows, degrade service quality, or lead to data manipulation or leakage if the application processes sensitive information. While the non-root execution context limits system-wide compromise, attackers could leverage this foothold to pivot within the network or escalate privileges if other vulnerabilities exist. Organizations in sectors heavily reliant on AI-driven automation, such as finance, healthcare, and critical infrastructure, may face operational disruptions or reputational damage. Additionally, since the vulnerability involves an API endpoint, automated or scripted attacks could be feasible if the endpoint is exposed or insufficiently protected, increasing the attack surface.
Mitigation Recommendations
1. Immediate upgrade to labsai EDDI version 5.5.0 or later to apply the official patch addressing the path traversal vulnerability. 2. Restrict access to the `/backup/import` API endpoint using network segmentation, firewall rules, or API gateway policies to ensure only authorized and authenticated users or systems can invoke this endpoint. 3. Implement strict input validation and sanitization on all file upload and extraction processes, including verifying that extracted file paths remain within the intended directory boundaries before writing to disk. 4. Employ runtime application self-protection (RASP) or file integrity monitoring to detect unauthorized modifications to application files such as JAR libraries. 5. Conduct regular audits and monitoring of application logs for unusual activity related to backup imports or file writes. 6. Use containerization or sandboxing to isolate the EDDI application environment, limiting the impact of potential code execution. 7. Review and enforce the principle of least privilege for the application user (UID 185), ensuring it has minimal permissions necessary to operate. 8. If upgrading immediately is not feasible, consider disabling or restricting the `/backup/import` endpoint temporarily until a patch can be applied.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Belgium, Italy
CVE-2025-32779: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in labsai EDDI
Description
E.D.D.I (Enhanced Dialog Driven Interface) is a middleware to connect and manage LLM API bots. In versions before 5.5.0, an attacker with access to the `/backup/import` API endpoint can write arbitrary files to locations outside the intended extraction directory due to a Zip Slip vulnerability. Although the application runs as a non-root user (`185`), limiting direct impact on system-level files, this vulnerability can still be exploited to overwrite application files (e.g., JAR libraries) owned by the application user. This overwrite can potentially lead to Remote Code Execution (RCE) within the application's context. This issue has been patched in version 5.5.0.
AI-Powered Analysis
Technical Analysis
CVE-2025-32779 is a path traversal vulnerability classified under CWE-22, affecting the labsai EDDI (Enhanced Dialog Driven Interface) middleware, which is used to connect and manage large language model (LLM) API bots. Specifically, versions of EDDI prior to 5.5.0 contain a Zip Slip vulnerability in the `/backup/import` API endpoint. This vulnerability allows an attacker with access to this endpoint to write arbitrary files outside the intended extraction directory by manipulating the paths within a crafted ZIP archive. Although the application runs under a non-root user (UID 185), which limits the ability to overwrite critical system files, the attacker can overwrite application files owned by this user, such as JAR libraries. Overwriting these files can lead to remote code execution (RCE) within the context of the application, potentially allowing an attacker to execute arbitrary code, manipulate application behavior, or escalate privileges within the application environment. The vulnerability has been addressed in version 5.5.0 of EDDI, and no known exploits are currently reported in the wild. The issue arises from improper validation and sanitization of file paths during ZIP extraction, enabling directory traversal beyond the designated extraction folder.
Potential Impact
For European organizations using labsai EDDI middleware versions prior to 5.5.0, this vulnerability poses a significant risk. Successful exploitation could lead to unauthorized code execution within the application context, potentially compromising the integrity and availability of services relying on EDDI for LLM API bot management. This could disrupt automated workflows, degrade service quality, or lead to data manipulation or leakage if the application processes sensitive information. While the non-root execution context limits system-wide compromise, attackers could leverage this foothold to pivot within the network or escalate privileges if other vulnerabilities exist. Organizations in sectors heavily reliant on AI-driven automation, such as finance, healthcare, and critical infrastructure, may face operational disruptions or reputational damage. Additionally, since the vulnerability involves an API endpoint, automated or scripted attacks could be feasible if the endpoint is exposed or insufficiently protected, increasing the attack surface.
Mitigation Recommendations
1. Immediate upgrade to labsai EDDI version 5.5.0 or later to apply the official patch addressing the path traversal vulnerability. 2. Restrict access to the `/backup/import` API endpoint using network segmentation, firewall rules, or API gateway policies to ensure only authorized and authenticated users or systems can invoke this endpoint. 3. Implement strict input validation and sanitization on all file upload and extraction processes, including verifying that extracted file paths remain within the intended directory boundaries before writing to disk. 4. Employ runtime application self-protection (RASP) or file integrity monitoring to detect unauthorized modifications to application files such as JAR libraries. 5. Conduct regular audits and monitoring of application logs for unusual activity related to backup imports or file writes. 6. Use containerization or sandboxing to isolate the EDDI application environment, limiting the impact of potential code execution. 7. Review and enforce the principle of least privilege for the application user (UID 185), ensuring it has minimal permissions necessary to operate. 8. If upgrading immediately is not feasible, consider disabling or restricting the `/backup/import` endpoint temporarily until a patch can be applied.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-04-10T12:51:12.278Z
- Cisa Enriched
- true
Threat ID: 682d984ac4522896dcbf76cb
Added to database: 5/21/2025, 9:09:30 AM
Last enriched: 6/21/2025, 5:09:55 PM
Last updated: 8/11/2025, 3:12:36 AM
Views: 10
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.