T09 · Insecure Skill Coding Practices
- Location
skills/smyx_common/scripts/util.py:341- Finding
Authentication Credentials Exposed in Process Logs
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s stated video risk-analysis purpose is coherent, but it handles sensitive health and surveillance data while under-disclosing account creation, token storage, and credential exposure risks.
Review before installing. This skill may upload sensitive videos, images, stream URLs, identifiers, and risk results to external services, can create or reuse a remote account without an explicit separate consent step, and stores/logs reusable tokens locally. Do not use it with private health or surveillance footage unless the publisher documents account handling, token protection, report access controls, alert recipients, retention, and dependency updates.
skills/smyx_common/scripts/util.py:341Authentication Credentials Exposed in Process Logs
skills/smyx_common/scripts/dao.py:57Authentication Tokens Persisted in Plaintext SQLite Storage
scripts/risk_analysis.py:249Historical Risk Report Query Is Sent Without the Required User Filter
skills/smyx_common/scripts/util.py:287Supplying a User Identifier Can Trigger Undisclosed Silent Remote Registration
skills/face_analysis/scripts/skill.py:75Mutable Default Parameter Can Leak Media URLs Across Analysis Requests
The requirements file pins Authlib to a version identified by the scanner as carrying multiple critical advisories, including authentication and cryptographic verification flaws. In a skill that may process alerts, identities, APIs, or tokens, vulnerable auth/JWT/JWE handling can enable forgery, bypass, or account/session compromise.
GitPython is pinned to a version with multiple critical advisories including command injection and unsafe option forwarding. If the skill clones repositories, inspects git state, or handles repository paths from external input, this can yield remote code execution or unauthorized file operations.
langchain-core is pinned to a version with multiple critical advisories including SSRF and prompt/template injection classes of issues. In an agentic skill that may fetch URLs, count tokens on image URLs, or render templates from dynamic content, these flaws materially raise the risk of internal network access, secret leakage, and unintended tool invocation.
The requirements file pins Authlib 1.6.6, and the finding lists multiple serious advisories including cryptographic and token-validation weaknesses. In a skill that likely handles authentication, API access, or signed tokens for video/alert workflows, vulnerable auth libraries can enable authentication bypass, token forgery, or cryptographic attacks.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
Automatic login/account creation, token handling, credential persistence, and billing/recharge flows are major undeclared behaviors unrelated to the stated feature. These functions expose users to privacy, authentication, and financial risk while preventing informed consent about account and payment side effects.
The skill describes sending anomaly footage, risk type, and location to external recipients, but it does not present a clear privacy warning or consent flow for transmitting highly sensitive surveillance and health-related data. This is especially dangerous given the context: elderly care, medical precursor inference, continuous monitoring, and location sharing amplify harm if data is over-collected or disclosed.
The instructions explicitly tell the agent to read an api-key from local configuration files and reuse it as a user's open-id. This is a direct secret-handling flaw: it repurposes stored credential material for user identity, encourages local secret discovery, and risks exposing or misusing privileged API keys during normal operation.
The workflow instructs collection of an open-id as a username or phone number without a clear privacy notice, minimization rationale, or handling policy. Collecting personal identifiers in a health/surveillance context materially raises privacy and compliance risk, especially when tied to historical reports and external APIs.
Click is pinned to a version reported as vulnerable to command injection. If this skill exposes CLI wrappers, task runners, or passes user-controlled values into command-related functionality, exploitation could lead to arbitrary command execution on the host.
Cryptography 3.4.8 is old and flagged for multiple serious issues, including oracle-style attacks and bundled vulnerable OpenSSL concerns. Because this skill likely communicates with external services and may sign or validate tokens, cryptographic weaknesses can undermine confidentiality and integrity.
httplib2 is flagged for decompression-bomb denial-of-service. A network-facing skill that fetches remote resources, model inputs, or media can be forced into excessive memory/CPU consumption through crafted compressed responses.
The pinned idna version is reported as vulnerable to specially crafted input handling issues. In systems that accept external URLs, domains, or callback endpoints, IDN parsing flaws can contribute to validation bypass, spoofing, or misrouting.
langchain-openai is reported vulnerable by published advisories. Because this package mediates model requests and potentially tool/response handling, weaknesses here can expose secrets, alter model interactions, or broaden prompt-injection impact.
langgraph is pinned to a version with known security advisories. In a workflow/agent orchestration context, framework flaws can affect state handling, tool execution, and boundaries between trusted application logic and untrusted model outputs.
langgraph-checkpoint is reported with multiple advisories, which is significant because checkpoint/state persistence often contains conversation context, credentials, or decision traces. Compromise here can lead to state tampering, data exposure, or unsafe resumption of privileged flows.
Detected: suspicious.install_untrusted_source