T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:53- Finding
Overprivileged Mailbox Access and Insecure Long-Lived Bearer Token Storage
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 53–61
Vulnerability Type: Excessive mailbox permissions and insecure credential-storage guidance
Risk Level: MediumComplete Vulnerable Snippet
markdown The six-digit code is emailed and lives for a few minutes. `/auth/request` always answers `202` whether or not the address has an account — it will not tell you which, so a wrong address looks exactly like a right one. **This is the step to plan for.** An agent running unattended needs read access to a mailbox — an IMAP account, a mail API, or a human who pastes the code once. Do this first and cache the token; it is a bearer token, sent as `Authorization: Bearer <token>` on everything below, and it lasts far longer than a deployment takes.Technical Analysis
The Skill recommends giving an unattended agent read access to a mailbox so that it can retrieve a short-lived authentication code. General IMAP or mail API access can grant visibility into unrelated messages and sensitive account-recovery information, exceeding the minimum privilege needed to retrieve one AgentsPodium verification code.
The Skill also directs the agent to cache a bearer token that remains valid substantially longer than the deployment operation. It does not prescribe encrypted secret storage, restrictive file permissions, log redaction, token lifecycle controls, or deletion after use. A bearer token requires no additional proof of identity; any party that obtains it can exercise its associated account permissions until it expires.
No evidence shows that the Skill intentionally transmits mailbox contents or credentials to an attacker. The issue is unsafe access and secret-management guidance rather than confirmed credential exfiltration.
Attack Path
- An operator grants the unattended agent general IMAP or mail API access to a mailbox.
- The agent retrieves the AgentsPodium authentication email ...[truncated 1179 chars]
- Remediation
View remediation
Remediation Suggestions
- Prefer one-time human entry of the verification code rather than unattended mailbox access.
- If automation is necessary, use a dedicated mailbox that receives only AgentsPodium authentication messages.
- Use a narrowly scoped mail API that can access only the required sender, label, folder, or message type instead of granting general IMAP access.
- Store the bearer token in an operating-system secret manager or managed secrets vault, never in plaintext files, prompts, shell history, or logs.
- Restrict token access to the deployment process and apply least-privilege filesystem and runtime permissions.
- Redact authentication codes and bearer tokens from application, HTTP, and diagnostic logs.
- Define token expiration, rotation, revocation, and cleanup procedures. Delete the cached token after the workflow when continued access is unnecessary.
- Isolate the deployment agent from untrusted skills, tools, users, and workloads that could inspect its environment or secret store.
- Update the Skill documentation to warn explicitly that primary or personal mailboxes must not be connected.