T09 · Insecure Skill Coding Practices
- Location
scripts/quickstart.py:25- Finding
OpenSearch Credentials and API Data Transmitted over Plaintext HTTP
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly does what it says, but it should be reviewed because it uses OpenSearch credentials with a hardcoded plaintext HTTP setting and can write sample data to a live datasource.
Install only if you are comfortable reviewing or changing the client configuration to use HTTPS, and run the quickstart only against a test or disposable OpenSearch datasource with narrowly scoped credentials. Pin the SDK version before relying on it in production.
scripts/quickstart.py:25OpenSearch Credentials and API Data Transmitted over Plaintext HTTP
SKILL.md:17Unpinned Third-Party SDK Installation Creates Supply-Chain Exposure
The skill instructs use of multiple sensitive environment variables, including service credentials, but does not declare any explicit tool scope or permissions boundary. In agentic environments, missing scope metadata can cause the runtime or reviewer to underestimate the skill's access to secrets and external network operations, increasing the chance of unintended credential exposure or unauthorized API use.
This code reads OPENSEARCH_USERNAME and OPENSEARCH_PASSWORD to authenticate outbound requests, but it provides no disclosure that credentials will be consumed or used for network access. The existing stderr message only reports missing variables and does not warn the user about handling sensitive values.
The script pushes documents to the configured OpenSearch datasource, which is a remote write operation affecting stored data. Although it prints "Pushing docs...", that status message does not warn the user that running the quickstart will add documents to a live datasource.
No suspicious patterns detected.