Back to skill

Security audit

Skill Digico Mixer

Security checks for vulnerabilities and agentic risk

Overview

The skill is purpose-related to mixer control, but it can send real commands to live audio equipment without enough scoping, confirmation, or endpoint validation.

Install only if you intend to control DiGiCo mixers on a trusted, isolated management network. Treat the state-changing actions as capable of affecting live sound immediately, and add operational safeguards such as target allowlists, operator confirmation, dry-run behavior, real endpoint verification, logging, and pinned dependencies before production use.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (3)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
skill_digico_mixer_impl.py:72
Finding

Unauthenticated Remote Control of Audio Equipment

Content
View full analysis
Dict: """ 连接DiGiCo调音台 Args: ip: 调音台IP地址 port: OSC端口 Returns: dict: 连接结果 """ if not OSC_AVAILABLE: return { "status": "error", "message": "python-osc库未安装,无法连接" } try: self.ip = ip self.port = port # 创建OSC客户端 self.client = udp_client.SimpleUDPClient(ip, port) # 测试连接 ping_result = self._ping() if ping_result["status"] == "success": self.connected = True return { "status": "success", "ip": ip, "port": port, "latency_ms": ping_result["latency_ms"], "message": f"已连接到DiGiCo调音台 {ip}:{port}" } else: return { "status": "error", "message": f"无法连接到 {ip}:{port},网络不通或OSC端口未开放" } ``` A representative state-changing operation is: ```python try: # 发送OSC消息 osc_path = self.osc_paths["scene_load"] self.client.send_message(osc_path, scene_id) return { "status": "success", "scene_id": scene_id, "osc_path": osc_path, "message": f"场景 {scene_id} 加载请求已发送" } except Exception as e: return { "status": "error", "message": f"场景加载失败:{str(e)}" } ``` ### Technical Analysis The controller accepts an arbitrary IP address and UDP port and creates an OSC client without authenticating the caller or establishing that the caller is authorized to control the selected mixer. After the weak connectivity test succeeds, the controller marks itself as connected and permits st ...[truncated 1760 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
skill_digico_mixer_impl.py:108
Finding

UDP Connect Is Incorrectly Treated as Proof of Mixer Connectivity

Content
View full analysis
Dict: """测试调音台连接性""" try: # 发送ping OSC消息 start_time = time.time() # 使用socket测试连接性 sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.settimeout(self.timeout) try: sock.connect((self.ip, self.port)) latency = (time.time() - start_time) * 1000 sock.close() return { "status": "success", "latency_ms": round(latency, 2) } except socket.timeout: return { "status": "error", "message": "连接超时" } finally: sock.close() except Exception as e: return { "status": "error", "message": str(e) } ``` ### Technical Analysis Calling `connect()` on a UDP socket does not establish a network session or require the remote endpoint to respond. It generally records the default peer address locally and may succeed when no service or device exists at the destination. The function does not send the documented OSC ping message, wait for a response, validate a nonce, or verify the identity of the responding equipment. Nevertheless, it reports success and calculates “latency” from the duration of the local `connect()` operation. The `connect()` method then uses this result to set `self.connected = True`. Consequently, both endpoint availability and the displayed latency are misleading. Commands can subsequently be transmitted to an absent, unintended, or non-DiGiCo endpoint while the application reports that a mixer was successfully connected. ### Attack Path 1. A caller supplies an arbitrary routable IP address and UDP port. 2. `_ping()` creates a UD ...[truncated 930 chars]
Remediation
View remediation

T08 · Insecure Dependencies

Note
Location
SKILL.md:194
Finding

Unpinned Third-Party OSC Dependency

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (11)

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

The declared description says this skill is a DiGiCo mixer OSC protocol remote control system, which implies network-based OSC messaging to control actual mixer hardware. However, the code only defines a basic library class that stores device info and configuration in dictionaries and reports status with a timestamp. There is no OSC handling, no networking, no remote control logic, no message formatting, and no interaction with external devices. While the subject area (DiGiCo mixers) is aligned, the implemented behavior is materially different from the declared primary purpose.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill documents live remote-control actions such as scene switching, channel gain changes, routing, and snapshot operations without clearly warning that these actions can immediately alter production audio output. In a live sound environment, accidental or uninformed use could interrupt performances, mute feeds, create unsafe level changes, or disrupt critical broadcast/theater operations.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill explicitly promotes unattended scheduled monitoring/automation against production audio equipment without warning about the risks of autonomous execution in a live environment. Even monitoring workflows can evolve into automated responses or repeated command issuance, and unattended interaction with core audio infrastructure can amplify mistakes, cause service disruption, or interfere with time-critical operations.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The manifest description says this skill is a 'DiGiCo mixer OSC protocol remote control system', which implies networked OSC communication and actual mixer control. However, the implementation only stores device and configuration dictionaries in memory and exposes generic add/remove/list/status helpers, without any OSC protocol handling or remote control operations.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The module docstring states the skill remotely controls and monitors a DiGiCo mixer, suggesting real device state observation. However, get_status explicitly notes that status query is simulated and merely returns cached/local fields rather than obtaining mixer state, which is a direct contradiction for the monitoring claim.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

Natural-language strings and metadata throughout the file are exclusively in Chinese, including the module description and user-facing messages, with no indication that language is configurable or user-selected. Under the policy, forcing a specific language without opt-in is a natural-language policy concern.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

This skill can send live control commands to a remote mixer, including scene loads and channel processing changes, without any confirmation, safety interlock, dry-run mode, or authorization guard. In a production or broadcast environment, accidental or unauthorized invocation could immediately disrupt audio, cause loss of service, or create hazardous output conditions.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
95% confidence
Finding

The file’s user-facing natural-language strings and docstrings are written exclusively in Chinese, including the skill name and method descriptions. This can violate a language/locale policy when no user choice or justification is provided for restricting the skill to a specific language.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

The skill establishes UDP/OSC communication to a remote device and later transmits control data, but the code does not provide an upfront user warning that actions will be sent over the network to the specified mixer IP/port. This is a user-disclosure gap for network operations in a code file, especially because the module supports automated invocation.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

The connect flow presents itself as connecting to the mixer and _ping is documented as testing mixer connectivity, while comments say it sends a ping OSC message. In reality, _ping never sends an OSC ping or validates a mixer response; it only invokes UDP socket.connect, which does not prove the remote mixer is present or speaking OSC.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
99% confidence
Finding

Within _ping, the comment explicitly states that a ping OSC message is being sent. The implementation only creates a UDP socket and calls connect on it, with no OSC payload transmission through self.client or the socket, so the comment directly contradicts the code.

Content

No source excerpt is available for this finding.