Back to skill

Security audit

emby-manager

Security checks for vulnerabilities and agentic risk

Overview

This Emby management skill is purpose-aligned, but it needs review because it handles powerful API keys insecurely and suggests broad administrator commands without enough guardrails.

Install only if you are comfortable giving the agent an Emby API key and using it for live server administration. Prefer HTTPS, avoid putting API keys in URLs when possible, do not paste keys into shared logs or transcripts, use a dedicated limited-scope key, and require explicit confirmation before deletes, user changes, restarts, firewall changes, or recursive permission commands.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (2)

T09 · Insecure Skill Coding Practices

Error
Location
SKILL.md:24
Finding

Emby API Credentials Exposed in Query Strings and Plaintext HTTP

Content
View full analysis
:" // 用户提供 const API_KEY = "" // 用户提供 // GET 请求 fetch(`${BASE}/endpoint?api_key=${API_KEY}`) // POST 请求 fetch(`${BASE}/endpoint?api_key=${API_KEY}`, { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({...}) }) ``` The API reference reinforces the insecure pattern: ```text GET http://:/System/Info?api_key= ``` ### Technical Analysis The Skill mandates query-string authentication and documents plaintext HTTP as the standard connection format. Query parameters are commonly retained in reverse-proxy logs, application access logs, browser or client history, monitoring systems, exception messages, and diagnostic output. Consequently, an Emby API key can be disclosed even if the response body is handled securely. When the server address uses HTTP, both the API key and returned data are transmitted without transport encryption. An attacker with visibility into the local network, an upstream gateway, or another network interception point could recover the key and sensitive Emby data. The network destination is the user-supplied Emby server and is necessary for the declared management functionality. There is no evidence of transmission to an unrelated or attacker-controlled service. The vulnerability is insecure credential transport rather than confirmed intentional exfiltration. ### Attack Path 1. A user supplies an Emby server URL and an API key. 2. The Skill constructs a URL containing `api_key=`. 3. The full URL is transmitted over HTTP or recorded by a client, proxy, se ...[truncated 992 chars]
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
references/troubleshoot.md:108
Finding

Overbroad Privileged Filesystem and Firewall Remediation

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (19)

Vague Triggers

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill mandates activation for essentially any Emby-related request without clear scope boundaries or exclusions. This can cause overbroad routing of user requests into a privileged management workflow, increasing the chance of unintended administrative actions, credential collection, or disclosure of sensitive server data when a lighter-weight response would have been sufficient.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill instructs the agent to collect an API key and retain it for the whole conversation, but gives no guidance on minimizing retention, masking display, or warning the user about sensitive credential handling. Because the API key grants direct access to Emby administrative APIs, improper storage, reuse, or accidental exposure could enable unauthorized control of the media server.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
78% confidence
Finding

整份 SKILL.md 从描述、步骤到输出规范均以中文固定表述,且未说明是否支持其他语言或由用户选择语言。按规则,若技能强制特定语言而没有用户选择或正当区域性说明,可能构成语言/locale 策略问题。

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

Generic trigger terms like 'scan', 'refresh', 'user', 'status', and 'logs' are likely to collide with unrelated contexts, causing accidental invocation of this skill. In a skill that can access server status, user information, and administrative endpoints, mistaken activation raises the risk of privacy exposure or unintended operational changes.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill explicitly supports access to playback history, active sessions, user details, and IP addresses without any privacy notice or access-control guidance. This can normalize disclosure of viewing behavior and network-identifying data to anyone who can trigger the skill, creating surveillance and privacy risks beyond ordinary server management.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The guide recommends passing the Emby API key in the query string as the simplest default approach, without warning that URLs are commonly exposed through logs, browser history, reverse proxies, monitoring tools, and referrer leakage. In a NAS/media-server management skill, this is especially risky because the same credential may grant broad administrative access to users, libraries, sessions, and destructive endpoints.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The reference lists destructive administrative operations such as deleting media items, deleting users, restarting the server, and running/stopping tasks with only minimal caution markers and no clear requirement for confirmation, authorization boundaries, or operational safeguards. In this skill context, an agent could translate casual user language into actions against a live Emby server, increasing the chance of accidental or unauthorized destructive changes.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The document goes beyond Emby API guidance and includes host-level Linux administration commands such as service management, log access, and filesystem inspection. In an agent skill context, this broadens the action surface from application management to operating-system control, increasing the risk of unsafe execution or privilege misuse if the agent follows the documentation automatically.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The guidance includes restarting the Emby service with sudo but does not clearly warn that this is a disruptive, system-impacting operation that can interrupt active streams and affect all users. In a skill used by an agent, omission of a warning and confirmation step makes unintended service disruption more likely.

Content

No source excerpt is available for this finding.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
89% confidence
Finding

The inclusion of a sudo command normalizes privileged execution within the skill documentation. In an agent setting, privileged commands are more dangerous because they can modify service state on the host and may be executed without adequate human review or environment checks.

Content

Scanner excerpt · references/media-ops.md (reported line 137)May include surrounding context.

md
systemctl status emby-server

# 重启 Emby 服务
sudo systemctl restart emby-server

# 查看 Emby 实时日志
journalctl -u emby-server -f

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · references/troubleshoot.md (reported line 23)May include surrounding context.

  1. 确认服务器 IP 和端口是否正确(默认 8096)
  2. 检查 Linux 防火墙:
    bash
    sudo ufw status
    sudo ufw allow 8096/tcp  # 如果被拦截
    
  3. 确认 Emby 服务正在运行:

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · references/troubleshoot.md (reported line 30)May include surrounding context.

  1. 确认服务器 IP 和端口是否正确(默认 8096)
  2. 检查 Linux 防火墙:
    bash
    sudo ufw status
    sudo ufw allow 8096/tcp  # 如果被拦截
    
  3. 确认 Emby 服务正在运行:

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · references/troubleshoot.md (reported line 135)May include surrounding context.

  1. 确认服务器 IP 和端口是否正确(默认 8096)
  2. 检查 Linux 防火墙:
    bash
    sudo ufw status
    sudo ufw allow 8096/tcp  # 如果被拦截
    
  3. 确认 Emby 服务正在运行:

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
86% confidence
Finding

Opening port 8096 via sudo ufw allow 8096/tcp changes the host firewall and can increase network exposure of the Emby service, especially if the server is internet-reachable. In this skill context, the command is relevant to troubleshooting, but presenting it without scoping advice or exposure warnings makes it risky.

Content

Scanner excerpt · references/troubleshoot.md (reported line 24)May include surrounding context.

  1. 检查 Linux 防火墙:
    bash
    sudo ufw status
    sudo ufw allow 8096/tcp  # 如果被拦截
    
  2. 确认 Emby 服务正在运行:
    bash

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The guide recommends recursive ownership and permission changes on a media directory without any warning about scope, least-privilege considerations, or the risk of breaking other services and weakening file protections. In an agent context, users may copy these commands verbatim against the wrong path, causing broad permission changes or unintended access exposure across the NAS.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The guide instructs stopping the Emby service and copying the full data directory without warning about downtime, backup size, sensitive contents, or filesystem space requirements. In a NAS management skill, this can lead to service disruption or accidental exposure/corruption of configuration and user data if executed carelessly or on constrained systems.

Content

No source excerpt is available for this finding.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
90% confidence
Finding

Stopping the service with sudo systemctl stop emby-server causes immediate service interruption and can impact active users or automations. In a troubleshooting skill, this may be legitimate, but issuing the command without warning or confirmation makes accidental disruption more likely.

Content

Scanner excerpt · references/troubleshoot.md (reported line 129)May include surrounding context.

bash
# 停止 Emby
sudo systemctl stop emby-server

# 备份数据库
cp -r /var/lib/emby/ /var/lib/emby_backup_$(date +%Y%m%d)

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
82% confidence
Finding

The session examples expose user activity, current media titles, and client IP addresses without any privacy or access-control warning. While these endpoints are legitimate for administration, documenting them without emphasizing sensitivity can normalize collection or disclosure of viewing history and network identifiers, which is more concerning in a household NAS/media context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
81% confidence
Finding

SQP-3 applies to all file types and includes language or locale policy violations. The skill content appears to force a specific language for all instructions without indicating user opt-in or that the skill is intentionally limited to Chinese-speaking users for a documented regional reason.

Content

No source excerpt is available for this finding.