Back to skill

Security audit

uos-printer-driver-downloader

Security checks for vulnerabilities and agentic risk

Overview

The skill does what it says, but it downloads driver packages and writes files using untrusted metadata without enough validation.

Review before installing. Use this only for intended UOS printer-driver downloads, prefer a controlled output directory, inspect driver_list.json if using the two-step flow, and verify any downloaded .deb through trusted vendor channels before installing it. Be aware that a compromised API response or edited cache file could cause unsafe file writes or save an untrusted package.

Vulnerability Patterns
  • 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
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (2)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/driver_utils.py:54
Finding

Path Traversal Through Untrusted Driver Metadata

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
scripts/driver_utils.py:72
Finding

Unvalidated Remote Download Target and Package Integrity

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Taint TrackingDirect Taint Flow, Variable-Mediated Taint Flow, Credential Exfiltration Chain
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (8)

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

The skill metadata understates behavior by not clearly declaring local file writes such as creating driver_list.json, while the documented workflow involves persistent local state and package downloads. This mismatch can mislead users and reviewers about what the skill actually changes on disk, reducing informed consent and making it easier for unsafe side effects to go unnoticed.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding

The skill declares capabilities to search, download, and save files, but it does not declare any explicit tool scope or permissions for network access and local file read/write. That creates an authorization and transparency gap: an agent may perform network and filesystem actions the user or platform did not clearly approve, increasing the risk of unintended downloads or file creation.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

This skill facilitates downloading executable software packages (.deb) onto the user's system but provides no explicit warning about the security risks of package installation, trust boundaries, or filesystem side effects. In context, package download functionality is inherently more dangerous than plain document download because users may later install the package, leading to code execution if the source, package integrity, or model matching is wrong.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The module docstring presents usage instructions entirely in Chinese, and the script's runtime messages are also Chinese-only. For a general-purpose utility, this is a natural-language policy issue because it imposes a specific language on users without opt-in or a documented regional justification.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

This code file contains natural-language strings that force a specific language for usage instructions and user interaction. Under the policy, language constraints should either be optional for the user or clearly justified as region-specific; neither is present here.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The module docstring is written entirely in Chinese, and all user-facing messages throughout the file are also hard-coded in Chinese. This indicates a language constraint presented without any opt-in, locale selection, or documented region-specific justification, which matches the language/locale policy violation criteria.

Content

No source excerpt is available for this finding.

Tainted flow: 'actual_url' from requests.get (line 75, network input) → requests.get (network output)

Medium
Category
Data Flow
Confidence
93% confidence
Finding

The code takes a download URL from a remote API response and immediately performs a second request to that URL without validating the scheme, host, or expected file type. This creates a server-side request forgery / untrusted redirect style risk and also allows downloading arbitrary content from an attacker-controlled endpoint if the upstream API, network path, or response is compromised.

Content

Scanner excerpt · scripts/driver_utils.py (reported line 77)May include surrounding context.

python
actual_url = result_data['data']['url']

        file_resp = requests.get(actual_url, headers=headers, stream=True, timeout=60)
        file_resp.raise_for_status()

        filename = f"{package}_{version}_{arch}.deb"

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
97% confidence
Finding

The module docstring and all user-facing prompts are written only in Chinese, which imposes a specific language on users. Under the policy, locale or language constraints should be optional or clearly justified; this file provides neither an opt-in nor documentation that the skill is region-specific.

Content

No source excerpt is available for this finding.