Back to skill

Security audit

Cn Cron Parser

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward Chinese-language cron expression helper with a normal optional dependency, and I found no hidden persistence, data access, exfiltration, or destructive behavior.

Before installing, be aware that the tool is intended for Chinese-language use and that its optional next-run feature depends on croniter. Install dependencies in a virtual environment and prefer a pinned, reviewed croniter version if supply-chain control matters.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:70
Finding

Unpinned Third-Party Dependency Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:70
Vulnerability Type: Unpinned and mutable third-party dependency
Risk Level: Medium

Vulnerable snippet:

text
- croniter (pip install croniter)

The dependency is imported at runtime by scripts/cn_cron_parser.py:65:

python
from croniter import croniter

Technical Analysis

The documented installation command retrieves the latest available croniter package and its transitive dependencies without enforcing a reviewed version, lock file, or cryptographic hashes. Consequently, the installed code can change after this Skill has been reviewed.

Python packages may execute code during installation or when imported. If the package repository, maintainer account, release process, or a transitive dependency is compromised, following the documented command could install attacker-controlled code. This is a supply-chain risk rather than evidence that the current croniter package is malicious.

Attack Path

  1. An attacker compromises the upstream package, its publishing account, its release pipeline, or one of its resolved dependencies.
  2. The attacker publishes a malicious release that is accepted by the unconstrained package requirement.
  3. A user follows the documentation and runs pip install croniter.
  4. Package installation or build hooks execute attacker-controlled code, or the malicious code is installed for later use.
  5. The user invokes the Skill with next-run calculation enabled.
  6. scripts/cn_cron_parser.py imports croniter, allowing malicious import-time code to execute with the privileges of the user running the script.

Impact Assessment

Successful exploitation could provide arbitrary code execution with the privileges of the user who installs or runs the dependency. Accessible resources may include that user's files, environment variables, credentials, network access, and any services available to the proces ...[truncated 356 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin croniter to a specifically reviewed version rather than installing the latest release.

  2. Maintain dependencies in a lock or requirements file with cryptographic hashes, and install them using hash verification:

    bash
    python3 -m pip install --require-hashes -r requirements.txt
    
  3. Generate and review hashes for the exact package artifacts and all transitive dependencies.

  4. Install dependencies inside a dedicated virtual environment rather than the system Python environment.

  5. Avoid privileged installation and execution; run the Skill using a least-privileged account.

  6. Use an approved package index or internal artifact repository that scans and retains reviewed package artifacts.

  7. Add automated dependency vulnerability and provenance checks to the release process.

  8. Periodically update the pinned version only after reviewing release changes and regenerating the lock file and hashes.

Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

The file name and content indicate a Chinese-language skill, and all user-facing instructions are presented only in Chinese. Under the policy rule, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale restriction is explicitly documented and justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
95% confidence
Finding

This code file contains user-facing descriptions, help text, and output entirely in Chinese, including the tool description and command usage. Under the natural-language policy rule, forcing a specific language without user opt-in can be a locale policy violation when no language choice or justification is provided.

Content

No source excerpt is available for this finding.