T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:6- Finding
Hardcoded External Document Destination Lacks Authorization Safeguards
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 6-16
Vulnerability Type: Excessive tool permissions and an unverified external write destination
Risk Level: MediumEvidence
yaml allowed-tools: [read, write, feishu_create_doc, feishu_update_doc, feishu_fetch_doc, message]The configuration also assigns the report destination to the Feishu knowledge-base identifier
7616288931050507220and a fixed test-report node.Technical Analysis
The Skill is intended to generate evaluation reports from user-supplied testing information. Such reports can contain security findings, defect descriptions, system architecture, deployment details, performance results, and release risks.
The Skill permits external Feishu document creation, update, and retrieval while prescribing a fixed knowledge-base destination. It does not require confirmation that the destination belongs to the user, verify that its audience is authorized to receive the report, offer a destination override, classify or redact sensitive content, or default to local storage before publishing externally.
The
messagecapability is also granted even though the documented report-generation workflow does not establish a need to send messages. This expands the available permission surface beyond the minimum capabilities explicitly required by the task.This is a least-privilege and authorization-boundary issue. Possession of the tool permissions does not itself prove that an external write will occur, but a runtime that follows the documented destination can publish sensitive material without sufficient destination-specific authorization checks.
Attack Path
- A user supplies internal testing data, including defects, security results, deployment details, or risk assessments.
- The Skill formats that information into an evaluation report.
- The report workflow uses the configured Feishu creation or update capability.
- The fixed k ...[truncated 1206 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the hardcoded Feishu knowledge-base and node destination.
- Require the user to select and explicitly confirm the destination before each external publication.
- Display the destination identifier, document visibility, and intended recipients in the confirmation prompt.
- Default to generating a local Markdown file and make external publication a separate opt-in action.
- Verify that the current user and runtime identity are authorized to write to the selected destination.
- Add a data-classification and redaction step for credentials, internal addresses, vulnerability details, personal data, and deployment information.
- Remove the
messagepermission unless a documented workflow requires it. If required, restrict recipients and require explicit approval before sending. - Separate read, create, and update operations so each invocation receives only the minimum tool capabilities required.
- Record external publication events, destination identifiers, approving users, and document identifiers in an audit log without storing sensitive report content unnecessarily.
