HarnessRouterの脆弱性で他組織の接続先を改ざん、修正版あり
Summary
HarnessRouterを複数組織向けに運用し、コンソールが自己ホストモードでない環境では、リモートから他組織のモデル接続先を書き換えられる脆弱性があります。0.31.8へ更新し、各組織の接続設定が意図したままか確認してください。
AI summary
Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.
HarnessRouterを複数組織向けに運用し、コンソールが自己ホストモードでない環境では、リモートから他組織のモデル接続先を書き換えられる脆弱性があります。0.31.8へ更新し、各組織の接続設定が意図したままか確認してください。
Original description The description as published by the source.
HarnessRouter is a self-hosted unified API for running agent harnesses with sessions, streaming, files, cancellation, and failure handling. Prior to 0.31.8, a console that is not in self-hosted mode attaches the server's internal key to requests carrying an Authorization header before validating the bearer, while the service-only PUT and GET /v1/orgs/{org}/connections/{name}, PUT /v1/orgs/{org}/policy/{backend}, and /internal/* routes trust that key and take the organization from the URL. In a multi-organization deployment, a remote caller can use a made-up bearer to rewrite another organization's provider connection to an attacker-controlled endpoint, causing later prompts to be disclosed and attacker-controlled responses to influence tasks. This issue is fixed in version 0.31.8.
Source: CVE.org (CVE Program・cvelistV5) NVD