T09 · Insecure Skill Coding Practices
- Location
skills/smyx_common/scripts/util.py:282- Finding
Credential and User Identifier Repurposed for Remote Account Registration
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches a remote facial-health analysis purpose, but it handles sensitive video, identity, credentials, logs, and persistent tokens in ways users should review before installing.
Install only after reviewing the remote data flow. Use a dedicated pseudonymous open-id rather than a phone number or secret, assume videos and report history go to the configured remote service, and avoid running this in a shared workspace until credential logging, plaintext token storage, automatic registration, and dependency scope are fixed.
skills/smyx_common/scripts/util.py:282Credential and User Identifier Repurposed for Remote Account Registration
skills/smyx_common/scripts/util.py:342Authentication Tokens and Sensitive Request Data Exposed Through Unconditional Logging
skills/smyx_common/scripts/dao.py:56Authentication Tokens and User Profile Data Stored in Plaintext SQLite Database
requirements.txt:1Excessive and Inconsistent Runtime Dependency Set
Authlib is pinned to a version flagged with numerous critical advisories affecting token/JWE/JWT handling, including signature validation bypass and padding-oracle style issues. In a skill that uploads videos or fetches network URLs and calls server-side APIs, compromised auth or token validation can enable account/session abuse, request forgery, or unauthorized access to protected backend functionality.
GitPython is pinned to a version with multiple critical advisories including command injection and unsafe option forwarding. If the skill or its surrounding agent ecosystem ever processes repositories, refs, tags, or git config values from untrusted input, this can lead to arbitrary command execution on the host.
langchain-core has multiple critical advisories including SSRF and prompt/template injection classes. This is highly relevant because the skill explicitly accepts network video URLs; vulnerable framework components can turn crafted inputs into server-side requests to internal resources or unsafe template execution paths.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill explicitly supports retrieving historical reports, using a persistent user identifier, and saving results to local files, but the description omits those behaviors. Hidden persistence and identity-linked history increase privacy and data-governance risk, especially for health-related outputs.
The skill auto-triggers for nearly any user-provided video unless a few excluded topics are mentioned, which is overly broad for a workflow that can upload user media, read config, and invoke local scripts. Broad trigger rules can cause unintended execution on unrelated content and expand the chance of privacy-impacting or user-surprising actions.
A delete operation for records identified by cameraSn is not justified by a user-facing skill whose stated purpose is submitting videos for facial diagnosis and returning results. If exposed through the agent, this could allow destructive actions against backend assets or records unrelated to diagnosis, creating integrity and availability risk.
The skill reads the entire local file and uploads its contents to a remote API without any user-facing disclosure in this file. Since facial videos are highly sensitive biometric/health-related data, silent exfiltration to a remote service raises significant privacy and compliance risks, especially if users believe processing is local or do not understand retention/sharing implications.
Click is pinned to a version with a reported command-injection advisory. If this dependency is used by administrative tooling, build scripts, wrappers, or any user-influenced CLI invocation around the skill, an attacker may be able to inject shell arguments or commands.
cryptography==3.4.8 is very old and carries multiple high-severity advisories, including timing-oracle and bundled OpenSSL issues. Because this skill interacts with remote URLs and server-side APIs, weak cryptographic primitives or vulnerable TLS/JWT-related operations materially increase risk of confidentiality and integrity compromise.
httplib2 is flagged for decompression-bomb denial of service via unbounded compressed responses. This is especially relevant here because the skill supports network video URLs, meaning attacker-controlled endpoints could return malicious compressed content and exhaust memory or CPU on the server.
idna is pinned to a version with advisories related to specially crafted internationalized domain inputs. In a skill that accepts network video URLs, improper IDNA handling can enable hostname confusion, filter bypass, or incorrect allow/blocklist decisions when validating remote sources.
langchain-openai is listed with high-severity advisories and operates at a trust boundary between user input, prompts, and model/tool interactions. If exploited, weaknesses here may enable data exposure, unsafe tool behavior, or bypasses in request handling that affect the server-side API workflow.
langgraph is pinned to a version with published advisories affecting the agent workflow layer. In an LLM-driven skill, vulnerabilities in orchestration and state-management libraries can permit unintended execution paths, data leakage between runs, or abuse of tool invocation logic.
langgraph-checkpoint is affected by multiple advisories and may expose risks in persisted execution state or recovery logic. If attacker-controlled data is checkpointed and later rehydrated unsafely, this can lead to data leakage, integrity issues, or abuse of resumed workflows.
langgraph-sdk is flagged with high-severity advisories and may affect remote graph/API interactions. Because this skill communicates with server-side services, weaknesses in the SDK can expose request/response data, enable unauthorized operations, or weaken boundary checks between components.
langsmith is pinned to a version with several high-severity advisories. Observability/tracing platforms often handle prompts, outputs, metadata, and sometimes secrets, so vulnerabilities here can amplify exposure of sensitive user video metadata, diagnosis results, or credentials.
oauthlib==3.2.0 has known security advisories affecting OAuth flows. Since this skill calls server-side APIs and may rely on bearer tokens or delegated access, weaknesses in OAuth processing can result in token leakage, improper validation, or authorization bypass.