T05 · Unauthorized Access and Privilege Escalation
Error
- Location
references/hardware-driver-integration.md:330- Finding
Broad USB Passthrough and World-Writable SDR Device Permissions
- Content
View full analysis
- Remediation
View remediation
Security audit
SDR Project Design
Security checks for vulnerabilities and agentic risk
Overview
The skill is a coherent SDR planning guide, but it includes under-scoped guidance for public-safety monitoring, broad USB access, exposed SDR network services, and unsafe install examples that users should review carefully.
Install only if you are comfortable treating it as a planning reference that may suggest privileged host changes. Before following its recipes, prefer device-specific USB access, avoid world-writable udev rules, bind SDR services only to trusted interfaces, use authentication or tunnels for remote access, pin and verify dependencies, and confirm local laws and privacy expectations before recording, archiving, summarizing, or sharing public-safety, sensor, meter, or other third-party radio traffic.
Vulnerability Patterns
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- 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
Findings (4)
T09 · Insecure Skill Coding Practices
Error
- Location
references/hardware-driver-integration.md:373- Finding
Unauthenticated SDR Services Exposed on Network Interfaces
- Content
View full analysis
- Remediation
View remediation
T03 · Remote Payload Retrieval and Execution
Error
- Location
references/general-desktop-and-utility.md:152- Finding
Mutable Remote Source Is Downloaded, Compiled, and Installed
- Content
View full analysis
- Remediation
View remediation
T08 · Insecure Dependencies
Warning
- Location
references/hardware-driver-integration.md:274- Finding
Unversioned SoapySDR Package Installation
- Content
View full analysis
- Remediation
View remediation
Vulnerability Patterns
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
- Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (12)
Chaining Abuse
High
- Category
- Tool Misuse
- Confidence
- 75% confidence
- Finding
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
- Content
HackRF
SUBSYSTEM=="usb", ATTR{idVendor}=="1d50", ATTR{idProduct}=="6089", MODE="0666", GROUP="plugdev"
text Reload with: `sudo udevadm control --reload-rules && sudo udevadm trigger` ### /dev/bus/usb bind mount (most reliable) ```yaml
Vague Triggers
Medium
- Category
- Not specified by scanner
- Confidence
- 87% confidence
- Finding
The description includes expansive triggers such as 'broad SDR research,' 'beginner orientation,' and 'to get any SDR project built in OpenClaw,' which are very wide activation conditions for a markdown skill file. It does not provide exclusion conditions or negative examples to clarify when a general SDR question should not invoke this skill.
- Content
Vague Triggers
Medium
- Category
- Not specified by scanner
- Confidence
- 94% confidence
- Finding
This markdown file includes activation guidance, so SQP-1 applies. The phrase 'when the user asks how an SDR dashboard should behave, or when a project needs a polished observatory UI' is somewhat ambiguous because 'needs a polished observatory UI' does not define clear scope boundaries or exclusions, which could cause the skill to be used for general UI design requests beyond the intended SDR context.
- Content
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
HackRF
SUBSYSTEM=="usb", ATTR{idVendor}=="1d50", ATTR{idProduct}=="6089", MODE="0666", GROUP="plugdev"
text Reload with: `sudo udevadm control --reload-rules && sudo udevadm trigger` ### /dev/bus/usb bind mount (most reliable) ```yaml
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 94% confidence
- Finding
The recipe explicitly suggests optional publishing/distribution for scanner and public-safety feeds but gives no warning about legal restrictions, privacy harms, or the sensitivity of dispatch audio and metadata. In an SDR planning skill, that omission can normalize building systems that expose real-time or archived public-safety communications, locations, and transcripts without considering jurisdictional limits or operational risk.
- Content
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 92% confidence
- Finding
The reference recommends AI summaries and call intelligence for public-safety communications without warning that generated outputs may be inaccurate, decontextualized, or expose sensitive operational details. In this skill's context, AI enrichment could amplify harm by producing misleading dispatch interpretations or making sensitive incidents easier to search, share, and act on.
- Content
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 91% confidence
- Finding
The document explicitly promotes self-hosted call archives and distribution workflows for public-safety radio traffic without any caution about jurisdiction-specific laws, privacy limits, or restrictions on rebroadcasting and retention. In the context of an agent skill that may turn this reference into actionable implementation guidance, that omission can normalize potentially unlawful interception, recording, or sharing of sensitive communications.
- Content
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 92% confidence
- Finding
The skill explicitly promotes a 'public-safety archive/search box' with SDR ingest, call recording, searchable playback, and mapping/statistics, but does not include any warning about jurisdiction-specific legality, privacy expectations, retention limits, or restrictions on rebroadcasting sensitive communications. In an agent skill, this omission can operationalize surveillance-style capabilities for end users without prompting safeguards, making misuse easier even if the underlying content is framed as legitimate SDR research.
- Content
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 90% confidence
- Finding
The skill recommends utility meter decoding and consumer-device monitoring via rtlamr and rtl_433-style workflows without clearly defining authorization and privacy boundaries. Because these tools can expose occupancy, consumption, or device telemetry about third parties, the lack of warnings or limitations lowers the barrier to unauthorized monitoring and normalizes collection of potentially sensitive household or utility data.
- Content
Missing User Warnings
Low
- Category
- Not specified by scanner
- Confidence
- 79% confidence
- Finding
This markdown file recommends using rtl_433 to decode consumer and weather sensor devices and then forwarding structured events to MQTT or files. Because this can capture and persist data from nearby devices, a brief user warning about privacy, authorization, or local data exposure would improve safety disclosure.
- Content
Missing User Warnings
Low
- Category
- Not specified by scanner
- Confidence
- 78% confidence
- Finding
The markdown instructs users to 'Normalize and write 16-bit PCM/WAV', which is a file-writing operation that can affect user data, but the document provides no warning or caution about creating output files, choosing safe paths, or possible overwrites. Under the markdown variant of SQP-2, user-facing descriptions should disclose behaviors that affect user data or system state.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 92% confidence
- Finding
The BladeRF example uses the filename 'rx样本.cf32', which introduces a Chinese-language term in a command example without any opt-in, explanation, or locale context. This can violate language/locale policy guidance because the skill implicitly mixes in a specific language rather than staying locale-neutral or offering a choice.
- Content