جزئیات آسیب‌پذیری

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.

• https://github.com/liketrek/TREK/pull/1520 x_refsource_MISC
• https://github.com/liketrek/TREK/commit/19064b39176660f3be3a2df198c87949504046e2 x_refsource_MISC
• https://github.com/liketrek/TREK/releases/tag/v3.3.0 x_refsource_MISC
• https://github.com/liketrek/TREK/security/advisories/GHSA-fmq9-ggh3-647p x_refsource_CONFIRM