ClawHub
Back to skill

Security audit

jira-ticket

Security checks for vulnerabilities and agentic risk

Overview

This skill does what it claims: it helps create Jira tickets using configured Jira credentials, with some ordinary but important privacy and credential-handling risks to manage.

Install only with a Jira token that has the minimum needed project permissions, set JIRA_BASE_URL to your exact HTTPS Atlassian tenant, and review ticket content before creation when it may contain confidential user input, internal details, or web-researched material.

A.I.G

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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 (2)

T09 · Insecure Skill Coding Practices

Error
Location
SKILL.md:137
Finding

Jira Credentials May Be Sent to an Unvalidated Network Destination

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:55
Finding

Unrestricted Research URL Fetching May Enable Server-Side Request Forgery

Content
View full analysis
Remediation
View remediation

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (3)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill performs creation of Jira tickets and may include user-supplied or web-researched content, but it does not require an explicit confirmation or warning that this content will be transmitted to an external SaaS platform. This creates a real privacy and data-handling risk because users may unintentionally send sensitive internal information or third-party content to Jira.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
93% confidence
Finding

This skill explicitly sends data to an external Jira API endpoint, including user-provided ticket content and potentially web-researched material. External transmission is expected for the skill's purpose, but it remains a real security concern because sensitive data could be exfiltrated to a third-party service without adequate review or minimization.

Content

Scanner excerpt · SKILL.md (reported line 167)May include surrounding context.

Phase 5 — Create the Ticket

bash
curl --http1.1 -s -X POST \
  -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
  -H "Content-Type: application/json" \
  "$JIRA_BASE_URL/rest/api/3/issue" \

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The skill documents use of Jira credentials via environment variables and Basic authentication, but it does not include a security notice about protecting secrets, avoiding echo/logging, or the sensitivity of using account-scoped API tokens. While common operational guidance, omission of these warnings can contribute to accidental credential exposure or misuse.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.