T09 · Insecure Skill Coding Practices
- Location
config.json:1- Finding
Hardcoded Jimeng Session Credential in Project Configuration
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is an image-generation proxy, but it ships and persists a real-looking Jimeng session credential and exposes the local API more broadly than its documentation suggests.
Review before installing. Replace and rotate any bundled Jimeng session, do not put your sessionid on the command line, restrict the service to 127.0.0.1 with trusted CORS/auth controls, and update vulnerable dependencies before exposing it to any network.
config.json:1Hardcoded Jimeng Session Credential in Project Configuration
scripts/jimeng.py:21Plaintext Session Storage and Exposure Through Command-Line Arguments
configs/dev/service.yml:1Local API Service Binds to All Network Interfaces with Unrestricted CORS
form-data 4.0.0 is a direct runtime dependency and the listed advisories include CRLF injection and weak randomness for multipart boundaries. In a service that uploads images or forwards multipart requests to upstream AI endpoints, malformed field names or predictable boundaries can enable request manipulation, parser confusion, or credential-bearing request corruption.
koa 2.15.3 is the core runtime web framework for this skill, so host-header injection, open redirect, and regex-complexity issues directly affect the externally reachable API surface. Because this service likely accepts user requests for image generation and file handling, framework-level request parsing and header handling bugs are highly relevant and can lead to denial of service, cache poisoning, redirect abuse, or trust-boundary failures.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
Enumerating local IPv4/MAC addresses, scheduling cron jobs, fetching arbitrary remote files, and converting them to base64 are unrelated to the declared image-generation purpose and strongly increase suspicion. In this skill context, such host-enumeration and persistence-oriented capabilities suggest possible reconnaissance, persistence, or data-staging behavior hidden behind a benign-looking AI tool.
The project includes axios 1.7.2, and the reported advisories include SSRF-related and prototype-pollution-adjacent issues that are relevant for a network-facing image-generation API skill. Because this skill likely fetches remote resources and interacts with external services, a vulnerable HTTP client increases the risk of request smuggling, proxy bypass, credential leakage, or attacker-controlled outbound requests.
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
lodash is a direct runtime dependency, and its historic and newly reported prototype-pollution and template/code-injection issues can become exploitable when user-controlled object paths or template strings are passed into helper functions. The lockfile alone does not prove exploitability, but this is a real risky dependency in a networked service that may transform user request objects.
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
No suspicious patterns detected.