T09 · Insecure Skill Coding Practices
- Location
references/xingkong-webapi.md:19- Finding
Plaintext HTTP Used for Password-Based ERP Authentication
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Kingdee ERP development skill is mostly coherent documentation, but it includes unsafe credential, authentication, and database-operation examples that users should review before installing.
Install only if you specifically need Chinese Kingdee K3 Cloud/Cosmic development help. Treat its WebAPI, admin-login, SSO, database restore, and production-operations snippets as drafts: require HTTPS, secret management, password rotation, least-privilege accounts, authorization checks, backups, and testing outside production before applying them.
references/xingkong-webapi.md:19Plaintext HTTP Used for Password-Based ERP Authentication
references/cangqiong-dev.md:485Weak MD5-Based API Request Signature
references/cangqiong-dev.md:559Bearer Token Exposed in Single Sign-On URL Query String
references/cangqiong-dev.md:281Custom API Template Omits Explicit Authorization and Leaks Internal Details
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<configuration>
<system.web>
<!-- 最大请求大小(KB),102400 = 100MB -->
<httpRuntime maxRequestLength="102400" executionTimeout="3600" />
<!-- Session 超时(分钟) -->
<sessionState timeout="60" />
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<configuration>
<system.web>
<!-- 最大请求大小(KB),102400 = 100MB -->
<httpRuntime maxRequestLength="102400" executionTimeout="3600" />
<!-- Session 超时(分钟) -->
<sessionState timeout="60" />
This is a direct exposure of default administrator credentials without an immediate warning to rotate them, which can facilitate compromise if copied into test, staging, or production deployments. Because the skill is specifically about Kingdee development and administration workflows, readers may treat the credentials as endorsed operational guidance.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# 金蝶云星空 WebAPI 接口开发
## 目录
- [概述](#概述)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# 金蝶云星空 WebAPI 接口开发
## 目录
- [概述](#概述)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# 金蝶云星空 WebAPI 接口开发
## 目录
- [概述](#概述)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# 金蝶云星空 WebAPI 接口开发
## 目录
- [概述](#概述)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# 金蝶云星空 WebAPI 接口开发
## 目录
- [概述](#概述)
The skill’s trigger scope is extremely broad, matching essentially any Kingdee-related development mention. In an agent system, this can cause unintended invocation and over-delegation, increasing the chance that unrelated requests are routed into this skill and that its instructions dominate safer or more appropriate behaviors.
The guidance states that fields involving Chinese names must use the _L table with FLOCALEID=2052, which hard-codes a specific locale in natural-language instructions. The file does not indicate user opt-in, alternatives for other locales, or a documented justification that this skill is intentionally restricted to a China-specific environment.
The authentication examples include app secrets, bearer tokens, signature headers, and even a login URL carrying a token, but do not warn readers against exposing these values in source control, logs, browser history, referrers, or monitoring systems. In an ERP development skill, readers may copy these patterns directly into production integrations, increasing the chance of credential leakage and account compromise.
The integration section normalizes direct database access and bulk synchronization between ERP systems without emphasizing change control, backups, idempotency, validation, transactional safety, or production impact. In a Kingdee/Cosmic enterprise integration context, such examples can lead to accidental corruption, inconsistent cross-system state, or high-impact outages if applied directly in live environments.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
The document states that all fields involving Chinese names must use FLOCALEID=2052 (Simplified Chinese), which is a natural-language locale requirement. Because the file does not offer a language choice or explain that the skill is intentionally limited to a China-specific environment, this creates a language/locale policy concern.
The file includes SQL restore commands with REPLACE, which can overwrite an existing database, but this section does not explicitly warn the reader about the destructive effect at the point of use. While the document discusses backups elsewhere, it does not clearly disclose that these commands may irreversibly replace target databases if run against the wrong instance or name.
The document tells users to run KILL 55 to terminate a blocking session. Although it says '谨慎使用', it does not clearly warn that killing a session can roll back in-flight work, disrupt users, or cause data loss for uncommitted transactions.
The cross-organization pricing example fetches target-organization price data using a supplied targetOrg ID but does not demonstrate any permission, organization-membership, or data-scope validation before performing the read. In a Kingdee multi-org environment, this can normalize insecure implementation patterns and lead developers to expose pricing or commercial data across organizations if the operation is reachable by users lacking access to the target organization.
The SQL example explicitly requires FLOCALEID = 2052, which forces Simplified Chinese locale behavior in natural-language guidance. Under the policy, locale-specific behavior should either be optional for the user or clearly justified as region-specific; this file provides neither.
This markdown file presents all skill guidance in Chinese from the title onward, which effectively forces a specific language for users consuming the template library. The policy allows fixed locale behavior only when the file offers user choice or clearly documents a justified regional constraint, neither of which appears here.
The entire skill is written as Chinese-only operational guidance, including field naming and UI instructions, with no indication that users may choose another language or that the skill is intentionally restricted to a Chinese-language environment. Under the stated policy, forcing a specific language without user opt-in can be a natural-language policy violation unless clearly justified.
The document presents default administrator credentials as a normal login option during environment setup, which normalizes insecure access practices. In a developer skill for ERP customization, this can lead users to retain or reuse well-known credentials in real environments, increasing the chance of unauthorized administrative access.
Including default administrator credentials in plain language creates a reusable secret pattern that may be copied into active environments or searched by attackers familiar with vendor defaults. Even if these are vendor-known defaults, documenting them without hardening guidance lowers the barrier to misuse and weakens secure setup practices.
The document presents username/password authentication over an http:// endpoint and does not warn that credentials must be protected in transit and at rest. This can normalize insecure integration patterns, leading users to transmit ERP credentials unencrypted or embed them directly into scripts, exposing high-value enterprise accounts.
This markdown file describes operations that can change business records and includes a delete endpoint, but it does not warn users that these actions may alter workflow state or permanently remove data. Under the markdown-specific warning criterion, behaviors affecting user data or system integrity should be accompanied by explicit cautionary language.
The title and entire document are written in Chinese, and there is no indication that users may choose another language or that the content is intentionally limited to a Chinese-only audience. Under the stated policy, forcing a specific language without opt-in can be a natural-language policy violation.