T09 · Insecure Skill Coding Practices
- Location
references/web_advanced_migration.md:48- Finding
Path Traversal in File Upload and Download Examples
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This migration guide does not appear to run hidden code, but several copy-ready examples teach unsafe authentication, file handling, and secret practices.
Review this skill before relying on its examples in real code. Treat the migration mappings as reference material, but replace the file upload/download, login/session, authorization filter, and configuration examples with secure implementations using canonical path checks, real token validation, password hashing or an identity provider, and environment-backed secrets.
references/web_advanced_migration.md:48Path Traversal in File Upload and Download Examples
references/config_system_migration.md:76Hardcoded Database Passwords and JWT Signing Secrets in Configuration Examples
references/web_advanced_migration.md:365Hardcoded Administrative Credentials in Session Login Example
references/web_filter_interceptor_migration.md:48Authentication Bypass Through Authorization Header Presence Check
Referenced artifact was not completely inspected
| 注解替换对照表 / 完整的 Spring→Solon 注解映射 | `references/annotation_mapping.md` | `@Autowired`, `@Inject`, `@RequestMapping`, `@Mapping`, `@Service`, `@Component`, `@Val
Referenced artifact was not completely inspected
| 注解替换对照表 / 完整的 Spring→Solon 注解映射 | `references/annotation_mapping.md` | `@Autowired`, `@Inject`, `@RequestMapping`, `@Mapping`, `@Service`, `@Component`, `@Val
Referenced artifact was not completely inspected
| 注解替换对照表 / 完整的 Spring→Solon 注解映射 | `references/annotation_mapping.md` | `@Autowired`, `@Inject`, `@RequestMapping`, `@Mapping`, `@Service`, `@Component`, `@Val
Referenced artifact was not completely inspected
| IoC 容器 / DI / 组件注册 / 作用域 / 生命周期 / AOP / 事件 / 包扫描 | `references/ioc_aop_migration.md` | `@Inject`, `@Configuration`, `@Bean`, `LifecycleBean`, `@Init`, `@Destr
Referenced artifact was not completely inspected
| 配置文件 / 属性注入 / 配置类 / Bean 定义 / 条件装配 | `references/config_system_migration.md` | `app.yml`, `@Inject("${")`, `@Configuration`, `@Bean`, `@Condition`, `solon.con
Referenced artifact was not completely inspected
| 配置文件 / 属性注入 / 配置类 / Bean 定义 / 条件装配 | `references/config_system_migration.md` | `app.yml`, `@Inject("${")`, `@Configuration`, `@Bean`, `@Condition`, `solon.con
Referenced artifact was not completely inspected
| 事务 / 缓存 / Redis / 陷阱清单 | `references/transaction_cache_migration.md` | `@Transaction`, `@Cache`, `Redis`, `@CacheRemove`, `CacheService` |
Referenced artifact was not completely inspected
| 事务 / 缓存 / Redis / 陷阱清单 | `references/transaction_cache_migration.md` | `@Transaction`, `@Cache`, `Redis`, `@CacheRemove`, `CacheService` |
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!-- Spring Before -->
<dependency>
<groupId>org.mybatis.spring.boot</groupId>
<artifactId>mybatis-spring-boot-starter</artifactId>
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<version>3.5.5</version>
</dependency>
<!-- Solon After:自 3.5.9 起 baomidou 官方发布 Solon 适配 -->
<dependency>
<groupId>com.baomidou</groupId>
<artifactId>mybatis-plus-solon-plugin</artifactId>
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<version>3.5.5</version>
</dependency>
<!-- Solon After:自 3.5.9 起 baomidou 官方发布 Solon 适配 -->
<dependency>
<groupId>com.baomidou</groupId>
<artifactId>mybatis-plus-solon-plugin</artifactId>
Line L025 states that when the user communicates in Chinese, all responses and code comments must be in Chinese. This imposes a language policy automatically based on user input rather than offering a choice or obtaining explicit opt-in, which matches the locale/language policy violation criteria.
The file title and all instructional content are presented in Chinese, and there is no indication that users may choose another language or that the document is intentionally limited to a China-specific or Chinese-speaking context. Under the policy, a skill or reference that effectively mandates a specific language without opt-in is a natural-language locale violation.
The document includes realistic-looking plaintext secrets and credentials in configuration examples, including a database password and a JWT secret, without clearly labeling them as placeholders or warning against real-world reuse. In a migration guide, readers may copy these examples directly into working applications, normalizing insecure secret handling and potentially causing accidental credential exposure if committed to source control.
The development environment example repeats hardcoded usernames and passwords in plaintext without any cautionary note. Even if intended as sample data, this can encourage unsafe copying patterns and teaches readers to store secrets directly in environment-specific YAML files, which are commonly checked into repositories.
The Solon-side migration examples again show plaintext database passwords and a JWT secret, which is especially risky because they appear in the 'after' target-state configuration that readers are expected to adopt. This reinforces insecure migration outcomes by presenting hardcoded secrets as an acceptable Solon configuration pattern.
This markdown file is entirely written in Chinese and presents the skill/reference content in a single language without any user opt-in or alternate locale option. Under the policy rule for natural-language violations, forcing a specific language is reportable unless the locale restriction is explicitly justified.
This markdown file is written entirely in Chinese and does not indicate that language selection is optional or user-configurable. Under the stated policy, forcing a specific language without user opt-in is a natural-language locale violation unless the locale restriction is explicitly documented and justified.
This markdown file presents all instructional content in Chinese and does not indicate that the user can choose another language or that the skill is intentionally restricted to a Chinese-speaking audience. Under the natural-language policy rule, forcing a specific language without user opt-in is a locale/language policy concern.
The upload and download examples concatenate user-controlled filenames directly into filesystem paths, which can enable path traversal (../), overwrite of arbitrary files, or unauthorized file read access if copied into production code. In a migration guide, this is more dangerous because readers are likely to reuse the sample verbatim as framework-approved practice.
At L434 and again at L464, the file asserts that one @Mapping can only map one path pattern and that multi-path mappings must be split into multiple methods. This is a concrete behavioral claim in migration guidance; if untrue, it creates a direct contradiction between documentation intent and actual code developers would write.
Lines L437 and L457 state that Solon has no @ControllerAdvice and that global exception handling must be implemented with Filter + try-catch. This is intent-level guidance embedded in documentation, and if inaccurate it would directly mislead developers about framework capabilities and migration strategy.
This markdown file presents the skill documentation entirely in Chinese and does not offer any language choice, translation note, or justification for a Chinese-only locale. The policy explicitly flags language or locale constraints when they are imposed without user opt-in or a documented region-specific need.
The file title and all instructional content are presented in Chinese, and there is no indication that users may choose another language or that the locale restriction is required for a region-specific purpose. Under the policy rules, natural-language content that implicitly forces a specific language without opt-in can be a locale policy concern.
This markdown file presents the entire skill reference in Chinese, beginning with a Chinese-only title and continuing throughout without offering a language option or stating that the content is intentionally region-specific. The policy explicitly flags language or locale constraints when they are imposed without user opt-in or documented justification.