IDURAR hat einen Path Traversal (unauthentifizierter Benutzer kann sensible Daten lesen)

The core of the vulnerability lies within the corePublicRouter.js file, where user input is directly appended to a join statement without proper sanitization. This lack of validation enables an attacker to craft malicious, URL-encoded payloads that bypass security checks. By strategically encoding directory traversal sequences (e.g., ../), an attacker can escape the intended path and access arbitrary files on the server. The potential impact includes exposure of configuration files, source code, and other sensitive data, potentially leading to complete system compromise. While the description doesn't explicitly mention it, successful exploitation could facilitate further attacks, such as remote code execution, depending on the files accessed.

Organizations utilizing IDURAR ERP CRM, particularly those running version 4.1.0 or earlier, are at risk. Shared hosting environments where multiple users share the same server instance are especially vulnerable, as a compromise of one user's account could potentially lead to access to other users' data or the entire system.

• nodejs / server:

grep -r 'corePublicRouter.js' /var/www/html/

• nodejs / server:

journalctl -u node -f | grep -i "path traversal"

• generic web: Inspect access logs for requests containing suspicious path traversal sequences like ../ or encoded equivalents (e.g., %2e%2e%2f). • generic web: Use curl to attempt path traversal: curl 'http://<target>/../../../../etc/passwd' (expect a 403 or similar error after mitigation).

1. 2024-10-04Disclosure

   disclosure

1. Reserviert2024-09-30
2. Veröffentlicht2024-10-04
3. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2024-47769 is to immediately upgrade IDURAR ERP CRM to version 4.1.1 or later, which contains the necessary fix. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) rule to block requests containing suspicious directory traversal sequences (e.g., ../, %2e%2e%2f). Additionally, restrict access to the vulnerable endpoint (corePublicRouter.js) to authorized users only. Regularly review and audit the application's code for similar vulnerabilities. After upgrading, confirm the fix by attempting to access a file outside the intended directory using a crafted URL; the request should be denied.