CyberRota Analysis
AI-GeneratedTREK versions prior to 3.3.0 are vulnerable due to an insecure settings API that allows authenticated users to store a malicious `llm_base_url`, which can be exploited to perform server-side request forgery (SSRF). This vulnerability can lead to unauthorized internal service discovery and potential exposure of sensitive infrastructure credentials, posing a significant risk to cloud resource integrity. Organizations using TREK, especially those with enabled LLM_PARSING features, should prioritize upgrading to version 3.3.0 to mitigate these risks.
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
TREK is a collaborative travel planner. Prior to 3.3.0, TREK allows an authenticated user to store an attacker-controlled llm_base_url through the settings API when the LLM_PARSING feature is enabled. Write permission to the target trip instance is required to trigger the vulnerable AI-assisted import path. The value is consumed by the clients in server/src/nest/llm-parse/clients/openai-compatible.client.ts, server/src/nest/llm-parse/clients/anthropic.client.ts, and server/src/nest/llm-parse/router/ollama-format.client.ts without applying the server-side request forgery guard. Triggering AI-assisted trip parsing causes the server to request the supplied destination, and upstream error response text can be returned in parsing warnings. This permits internal service discovery and access to link-local cloud metadata, with possible disclosure of infrastructure credentials and subsequent modification of protected cloud resources. This issue is fixed in version 3.3.0.