T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:68- Finding
Blanket Approval of Excessive macOS Permissions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 68–77
Vulnerability Type: Least-privilege violation through broad operating-system permission requests
Risk Level: MediumComplete vulnerable snippet:
markdown If no .yml snapshots appear here, it is almost always **MacOS permission-related**. Ask the user to run:playwright-cli open https://www.youtube.com --headed
text This will trigger macOS system dialogs for: - Screen Recording - Automation - Accessibility Approve all to enable snapshot generation.Technical Analysis
The skill tells users to approve Screen Recording, Automation, and Accessibility permissions collectively when browser snapshots are unavailable. This breaks the principle of least privilege because it does not establish that every listed permission is necessary for the narrow task of controlling YouTube in a browser.
Screen Recording may expose sensitive content displayed by other applications. Accessibility and Automation permissions may allow the authorized process to inspect user-interface elements, synthesize input, or control applications outside the intended browser workflow. The instruction also lacks per-permission justification, scope limitations, validation that the requesting executable is legitimate, and guidance for revoking permissions afterward.
No evidence in the audited files indicates that the skill itself exploits these permissions maliciously. The risk arises because the blanket instruction expands the capabilities available to
playwright-clior any compromised/spoofed process operating under the granted authorization.Attack Path
- Browser snapshot generation fails or appears to fail.
- The skill instructs the user to execute
playwright-cli open https://www.youtube.com --headed. - macOS presents one or more permission prompts for Screen Recording, Automation, or Accessibility.
- The user follows the unconditional ins ...[truncated 900 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the unconditional “Approve all” instruction.
- Determine which specific permission is required for the failing feature and request only that permission.
- Explain why each requested permission is needed and what data or applications it may expose.
- Instruct users to verify the executable identity and code signature before granting sensitive macOS permissions.
- Prefer browser accessibility snapshots or other mechanisms that do not require Screen Recording or system-wide Accessibility access.
- Offer non-privileged troubleshooting first, including checking whether the browser launched correctly, verifying the workspace snapshot directory, and restarting the named session.
- Provide revocation instructions through macOS System Settings after playback or troubleshooting is complete.
- If Automation permission is necessary, restrict it to the browser application rather than recommending broad approval for unrelated targets.