Security audit
Security checks for vulnerabilities and agentic risk
The ClickMeeting workflow is coherent, but its automatic setup can execute unverified remote code without separate user approval.
Review and approve the CLI installation separately before allowing setup, preferably using a pinned release with independently verified integrity. Connecting ClickMeeting lets OOMOL mediate access to meeting data and room tokens. The bundled instructions require confirmation for account changes, but the unavailable remote installer remains outside this inspection.
The supplied chunk only runs an external installer; it contains no ClickMeeting operations or evidence connecting the installation to ClickMeeting functionality. On the supplied evidence, this is a materially different behavior rather than an established supporting implementation detail. The downloaded script's contents and further effects are not available for assessment.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `create_conference` — Create a ClickMeeting meeting or webinar room. [write]
- `delete_conference` — Delete a ClickMeeting room. [destructive]
- `generate_access_tokens` — Generate access tokens for a token-protected ClickMeeting room. [write]
- `get_conference` — Get details for a ClickMeeting room.
- `get_session` — Get details for a ClickMeeting room session.
- `list_access_tokens` — List generated access tokens for a ClickMeeting room.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `generate_access_tokens` — Generate access tokens for a token-protected ClickMeeting room. [write]
- `get_conference` — Get details for a ClickMeeting room.
- `get_session` — Get details for a ClickMeeting room session.
- `list_access_tokens` — List generated access tokens for a ClickMeeting room.
- `list_all_recordings` — List all ClickMeeting recordings for the connected account.
- `list_chats` — List ClickMeeting chat archives available for download.
- `list_conference_recordings` — List recordings for a ClickMeeting room.
Piping a downloaded script directly into Bash executes mutable remote content without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. If the distribution endpoint or release pipeline is compromised, the installer can execute attacker-controlled code with the invoking user's permissions, potentially accessing local files and credentials.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
The setup instructions direct installation after a missing-command error without explicitly requiring approval for executing remote code and changing the local system. Confirmation requirements cover ClickMeeting mutations but not installation, creating an authorization gap; the conditional setup trigger limits exposure but does not establish user consent.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
## Resources