T08 · Insecure Dependencies
- Location
SKILL.md:64- Finding
Mutable Remote OpenAPI Schema Controls Privileged LINE API Operations
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:16-17,SKILL.md:64-67, andreferences/usage-patterns.md:5-9
Vulnerability Type: Mutable remote dependency without version or integrity pinning
Risk Level: MediumVulnerable Code
SKILL.md:14-18:markdown - `uxc` is installed and available in `PATH`. - Network access to `https://api.line.me`. - Access to the curated OpenAPI schema URL: - `https://raw.githubusercontent.com/holon-run/uxc/main/skills/line-openapi-skill/references/line-messaging.openapi.json` - A LINE Messaging API channel access token.SKILL.md:64-68:markdown 1. Use the fixed link command by default: - `command -v line-openapi-cli` - If missing, create it: `uxc link line-openapi-cli https://api.line.me --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/line-openapi-skill/references/line-messaging.openapi.json` - `line-openapi-cli -h`references/usage-patterns.md:5-9:bash command -v line-openapi-cli uxc link line-openapi-cli https://api.line.me \ --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/line-openapi-skill/references/line-messaging.openapi.json line-openapi-cli -hTechnical Analysis
The skill includes a locally reviewable OpenAPI document, but its installation workflow instead instructs UXC to retrieve the schema from the mutable GitHub
mainbranch. The URL is not pinned to an immutable commit, release artifact, or verified content digest.The retrieved schema defines the methods, paths, parameters, and request bodies exposed through
line-openapi-cli. Consequently, changes made upstream after this skill has been reviewed can alter the effective API command surface without changing the audited package. Because the generated client operates with a LINE channel bearer token, an unauthorized or compromised upstream schema could expose unexpected operations agai ...[truncated 2029 chars]- Remediation
View remediation
Remediation Suggestions
- Use the bundled, reviewed schema at
references/line-messaging.openapi.jsoninstead of retrieving a remote copy during setup. - If remote retrieval is required, replace the
main-branch URL with a URL pinned to a specific reviewed Git commit. - Publish and verify a SHA-256 or stronger cryptographic digest before allowing UXC to consume the downloaded schema.
- Store the verified schema locally and configure the generated client from that immutable local copy.
- Add validation that rejects schema changes to the expected server host, path allowlist, HTTP methods, and security scheme.
- Extend
scripts/validate.shto fail when documentation contains schema URLs referencing mutable branches such asmainormaster. - Require explicit user confirmation for every state-changing operation, including webhook endpoint updates and tests, not only message push and reply operations.
- Re-review and rotate the pinned schema version through a controlled release process whenever new API operations are needed.
- Use the bundled, reviewed schema at
