T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:317- Finding
Overbroad Feishu Document Permissions Recommended for Read-Only Retrieval
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 317
Vulnerability Type: Excessive application permissions
Risk Level: HighRelevant source excerpt, translated into English:
markdown A: Confirm that the application has been added as a document collaborator, or enable "all cloud-document permissions" for the application. For knowledge-base documents, add the application as a knowledge-base member and grant read permission. If another department created the document, contact the document owner for authorization.Technical Analysis
The Skill is designed to retrieve user-selected Feishu documents, spreadsheets, and knowledge-base entries. Document-level or knowledge-base-level read permission is sufficient for this declared functionality. Recommending that users enable all cloud-document permissions expands the application's authorization beyond the minimum required scope.
This is a least-privilege violation. If the Agent, its credentials, or any tool operating within the same authorization context is compromised or misused, the unnecessarily broad authorization could permit access to documents unrelated to the user's requested operation. The package contains no implementation demonstrating that tenant-wide access is technically required.
Attack Path
- A user attempts to retrieve a Feishu document and receives a permission error.
- The user follows the Skill's troubleshooting guidance and grants the application all cloud-document permissions.
- The application credential consequently gains access to a broader collection of organizational documents than the requested item.
- A compromised Agent session, exposed credential, malicious prompt, or misused API client submits requests for unrelated documents.
- Feishu authorizes those requests because of the excessive permission grant.
- Unrelated document, spreadsheet, Bitable, or knowledge-base content may be retrieved and exposed.
...[truncated 569 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the recommendation to enable all cloud-document permissions.
- Document the exact Feishu read-only scopes required for Wiki, Docx, Sheets, and Bitable operations.
- Prefer per-document collaboration grants or narrowly scoped knowledge-base membership.
- Separate optional bulk-export permissions from ordinary single-document retrieval permissions.
- Require explicit user confirmation before any operation traverses an entire knowledge space.
- Use dedicated credentials with read-only access and avoid sharing credentials across unrelated workflows.
- Provide a permission-denied error that identifies the missing resource-specific scope rather than recommending blanket authorization.
- Audit API activity and redact access tokens, document tokens, and sensitive content from logs.
