Back to skill

Security audit

jirac

Security checks for vulnerabilities and agentic risk

Overview

This Jira management skill clearly discloses its capabilities and requires confirmation before bulk or destructive changes.

Use the intended Jira account and project. Preview matching issues before approving bulk changes, take care with --force examples, and confirm attachment contents before uploading. The review covers the skill instructions, not a binary audit of jirac.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • 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
Findings (1)

Bulk mutation examples lack a warning to review affected issues before execution.

Medium
Category
Output Handling
Confidence
90% confidence
Finding

The bulk-flow recipes execute transitions, priority changes, comments, and archival across all matching issues; the priority update also includes --force. Although comments describe the actions, the file provides no caution about their bulk impact or instruction to inspect the matched issues before changing shared Jira data.

Content

No source excerpt is available for this finding.