ClawHub
Back to skill

Security audit

Dicom Segmentation Api

Security checks for vulnerabilities and agentic risk

Overview

This skill appears purpose-aligned for a DICOM segmentation API, but it handles sensitive medical uploads without privacy, access-control, or deployment-scope guidance.

Review before installing or running. Use only de-identified or properly authorized DICOM data, bind the server to localhost or a protected network unless you have deployed authentication and TLS, and verify the missing server code and dependency file before trusting this in any clinical or regulated environment.

A.I.G

Vulnerability Patterns
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill advertises DICOM upload endpoints for medical image segmentation but provides no warning that DICOM files may contain protected health information or other sensitive metadata. This can lead users to upload identifiable patient data to an API without understanding the privacy, compliance, and data-handling risks, especially in healthcare contexts where HIPAA/GDPR obligations may apply.

Content

No source excerpt is available for this finding.