T03 · Remote Payload Retrieval and Execution
- Location
references/workflow.md:26- Finding
Execution of Remotely Supplied Update Commands
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its stated PersonWise explainer purpose, but its update workflow gives too much trust to command text returned by the service or CLI.
Install only if you trust PersonWise, are comfortable with a user-level CLI install, browser OAuth, uploading selected product materials to the service, and using a course credit. Review any requested update command especially carefully; a safer design would construct update commands locally from fixed, validated metadata instead of executing command strings returned by the service or CLI.
references/workflow.md:26Execution of Remotely Supplied Update Commands
assets/bootstrap.ps1:20Insufficient Filesystem Identity Validation in Windows Installer
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
echo "Release executable checksum mismatch." >&2
exit 6
fi
chmod 700 "$candidate"
if [ "$(uname -s)" = "Darwin" ] && [ "$native_signature_status" = "verified" ]; then
codesign --verify --deep --strict --verbose=2 "$candidate"
spctl --assess --type execute --verbose=2 "$candidate"
The instruction to complete explicit link/embed/publication requests 'without asking again' can cause the agent to change sharing state autonomously, potentially exposing a generated product explainer more broadly than the user intended at the moment of execution. Because publication and link sharing affect data exposure and access control, skipping a fresh confirmation creates a meaningful risk of unintended disclosure.
Use presenter choices only for a concrete user requirement. Keep `run wait` active to terminal
state. Default omitted visibility to an explicit `distribution_target` of `private` — an omitted
target resolves to the OAuth grant's publication ceiling, which can be `link`; complete explicit
link/embed/publication requests without asking again. Return the URL matching the final access
mode only when final state proves playability: `access_mode=link` gives the public `share_url`;
`access_mode=private` gives the login-required `editor_url` and must be described as viewable only
after login, and state clearly that outsiders cannot open it. If sharing is needed, enable link access or ask the
This JSON manifest-style file contains service metadata and an encoded payload, but it does not provide any explicit trigger phrases, activation conditions, or exclusion constraints for when the skill should be invoked. For manifest files, missing specificity about trigger scope can lead to ambiguous or overly broad activation behavior if downstream systems infer invocation from generic metadata alone.
The only natural-language policy category in scope is language or locale policy violations. These lines describe an authentication flow but do not impose a language or locale requirement, so this does not clearly violate the stated policy.