CyberRota Analysis
AI-GeneratedAffected versions of Flowintel on Windows allow the LOG_FILE configuration to be modified, enabling administrators to set it to arbitrary filesystem paths. This vulnerability can be exploited by attackers to write controlled data into unintended files, potentially leading to code execution through manipulated logs. Organizations using Flowintel version 3.3.0 or higher should prioritize patching this vulnerability to mitigate the risk of unauthorized access and execution.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Affected versions of Flowintel allow the LOG_FILE configuration value to be modified through system settings without restricting it to a filename inside the intended log directory. Because the application constructs the log destination from this configurable value, an administrator could set LOG_FILE to an arbitrary filesystem path. Since attackers can influence logged content, this enables controlled data to be written into unintended files. The upstream commit specifically describes an exploitation chain in which an attacker injects a template into a chosen file and subsequently abuses application rendering behavior to execute code. The patch removes LOG_FILE from the web-editable settings, introduces validate_log_file_name() to reject absolute paths, traversal, Windows paths, null bytes, and directory components, and centralizes log path construction through resolve_log_file_path(). Version impacted: >=3.3.0