Back to skill

Security audit

Doro Git Essentials

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward Git command reference; it includes some destructive Git examples, but they are visible and aligned with the skill's stated purpose.

Install only if you want a general Git command cheat sheet. Before using destructive examples like git reset --hard, git clean -f/-fd/-fdx, or force pushing, check git status, make sure the affected work is backed up or no longer needed, and avoid running them on shared branches unless you understand the impact.

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
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • 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 (6)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
70% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

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

md
git pull --rebase

# Push changes
git push

# Push new branch
git push -u origin branch-name

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
65% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

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

md
git reset --soft HEAD~1

# Undo last commit (discard changes)
git reset --hard HEAD~1

# Revert commit (create new commit)
git revert commit-hash

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
65% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

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

md
git reset --soft HEAD~1

# Undo last commit (discard changes)
git reset --hard HEAD~1

# Revert commit (create new commit)
git revert commit-hash

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
70% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

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

git clean -fd

Include ignored files

git clean -fdx

text

## Common Workflows

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The markdown includes git reset --hard HEAD~1 and git reset --hard commit-hash, which can permanently discard uncommitted or newer committed work, but the surrounding description does not explicitly warn about data loss. Because this is a markdown file, safety-affecting behaviors should include clear warnings when they can impact user data or repository integrity.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The git clean -f, git clean -fd, and git clean -fdx examples remove untracked files and directories, potentially including ignored files, yet only a preview command is shown without an explicit warning that deletion may be irreversible. In markdown guidance, destructive operations affecting user data should be accompanied by clear cautionary language.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.