T05 · Unauthorized Access and Privilege Escalation
- Location
tools/xcheck.md:24- Finding
Automatic Cross-Model Review Can Disclose Sensitive Project Content to External Providers
- Content
View full analysis
Send to primary model: "Review this plan and identify issues" | | | +--> Primary model feedback | +--> Send to cross-check model: "Review the same plan independently" | +--> Cross-check model feedback ``` The cross-check prompt includes the reviewed material directly: ```markdown ## Content to Review [Paste code or plan here] ## Review Focus 1. Logic errors 2. Security issues 3. Performance risks 4. Maintainability ``` The example project configuration enables this behavior: ```yaml xcheck: true ``` ### Technical Analysis The cross-check workflow sends project plans or source code to an additional configured AI model. The instructions do not require: - Explicit user consent before transmission - Disclosure of the destination provider - A provider or region allowlist - Source-code sensitivity classification - Secret, credential, or personal-data scanning - Redaction or minimization of the transmitted payload - Confirmation that the secondary provider is covered by the project's confidentiality policy Because `xcheck` is enabled in the example configuration and is intended to run at critical decisions, after complex implementations, and before release, substantial proprietary material can cross the project's trust boundary. ### Attack Path 1. A project contains proprietary code, internal architecture details, customer-derived examples, or credentials embedded in configuration or source files. 2. The workflow reaches a configured cross-check point, such as a complex implementation or pre-release review. 3. T ...[truncated 901 chars]- Remediation
View remediation
