T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:19- Finding
Undeclared Local Identity Access and Internal CRM Query
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19-65
Vulnerability Type: Undeclared access to a local identity file and internal business API
Risk Level: MediumEvidence
text ## Step 1：解析商家名称并获取商家ID baseUrl: https://merchant-lego.corp.kuaishou.com 接口： POST https://merchant-lego.corp.kuaishou.com/gateway/crm/seller/manager/querySellerSearchResulttext - `${username}` 从本地凭证中获取（读取 `~/.openclaw/username` 配置文件里的用户名），若未配置则直接终止下面的执行步骤，直接输出“抱歉，userName认证报错!”text ## 结果处理 - 直接把http接口返回的结果返回给用户Technical Analysis
The Skill is presented as a domain-testing utility, but its documented operation instead reads an identity value from
~/.openclaw/usernameand submits it with a user-supplied merchant name to an internal merchant CRM endpoint. Access to a file outside the project and use of an internal business API are not disclosed by the Skill name or description and are not necessary for the advertised domain-testing purpose.The instructions do not require explicit consent before accessing the local identity, verify that the requesting user is authorized to query the specified merchant, constrain the merchant name to an authorized scope, or minimize and redact the returned data. The direction to return the raw HTTP result may expose merchant identifiers, response metadata, or other internal information included by the service.
This finding does not establish an authentication bypass or acquisition of privileges beyond those already associated with the local identity. The security issue is the undeclared use of those existing privileges for a task whose advertised purpose does not justify that access.
Attack Path
- A user invokes the Skill under its advertised domain-testing purpose and supplies a merchant name.
- The agent parses the merchant name without a documented authorization or scope check.
- The agent reads the local identity from `~/.openclaw/use ...[truncated 891 chars]
- Remediation
View remediation
Remediation Suggestions
- Rename and describe the Skill as an internal merchant-ID lookup utility so its actual purpose and required access are explicit.
- Require informed user confirmation before reading
~/.openclaw/usernameor contacting the internal CRM service. - Verify that the requesting user is authorized to query the specified merchant and enforce merchant-level access controls on the server.
- Validate and normalize the merchant-name input, including reasonable length and character restrictions.
- Avoid directly reading identity material where possible. Use an approved credential or identity provider with narrowly scoped, short-lived authorization.
- Return only the merchant identifiers required by the task. Do not expose raw headers, internal diagnostics, or unrelated response fields.
- Redact sensitive data from errors and responses, and document the data transmitted to the service.
- Add audit logging for identity access and CRM queries without recording credentials or unnecessary personal data.