T09 · Insecure Skill Coding Practices
- Location
scripts/ifa_to_codesys.ps1:51- Finding
Malformed Recipe Header Causes Unhandled Failure in Binary-to-Text Conversion
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a local PLC recipe converter, but its conversion scripts have material validation and serialization flaws that could produce unsafe or unusable recipe artifacts.
Review this skill carefully before using it in any PLC or production recipe workflow. It does not appear to steal data or persist on the system, but generated recipe files should be validated independently, especially numeric type widths and RecipeConfig.json schema checksums, before importing or deploying them.
scripts/ifa_to_codesys.ps1:51Malformed Recipe Header Causes Unhandled Failure in Binary-to-Text Conversion
scripts/fill_cam_data.ps1:46Malformed ProdData Header Causes Unhandled Cam-Data Processing Failure
scripts/codesys_to_ifa.ps1:88Value-Based Width Selection Corrupts Generated iFA Recipe Records
scripts/codesys_to_ifa.ps1:34Missing Recipe Configuration Fails Open with a Zero-Filled Schema Checksum
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
---
name: ifa-codesys-recipe
description: "Manage CODESYS PLC recipes via iFA Evolution �� create, modify, deploy recipe configurations"
tags: [domain-specific, plc, cli, file-based, report-generation]
This file contains user-facing natural-language documentation in a single fixed language, which can violate language/locale policy when no user opt-in or justification is provided. The synopsis, description, parameter text, and example are presented only in Chinese, and the file does not indicate that the skill is intended exclusively for a Chinese-speaking audience.
This PowerShell skill embeds its synopsis, description, and parameter help entirely in Chinese, which imposes a specific language/locale on users without any opt-in or alternative. The policy specifically calls out language or locale constraints as violations when the skill does not offer user choice or clearly justify the restriction.
No suspicious patterns detected.