Back to skill

Security audit

Certificate Management with cert-manager

Security checks for vulnerabilities and agentic risk

Overview

The skill supports legitimate certificate management, but its cluster-wide installation instructions lack clear limits and user control.

Confirm the target cluster, namespace, and requested changes before enabling writes. Approve cert-manager installation separately and review a pinned official release manifest. Check the email and domain names that issuance sends to Let's Encrypt, and use staging for tests. The supplied static scan reported no findings; Review rests on the installer’s insufficient controls, not the advisory scanner’s labels.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Generic keywords can activate the skill outside Kubernetes certificate management.

Medium
Category
Trigger Abuse
Confidence
97% confidence
Finding

The activation list includes everyday terms such as "secure", "encrypt", "renew", and "expiring" without requiring Kubernetes or cert-manager context. Although the description identifies a Kubernetes focus, these explicit mention-based triggers can match unrelated requests, and no exclusions constrain them.

Content

No source excerpt is available for this finding.

ACME issuance instructions omit disclosure of data sent to Let's Encrypt.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The workflow configures Let's Encrypt ACME issuers with an account email, and the certificate creation example selects the production issuer for the specified DNS names. It does not warn that account registration and issuance transmit the configured email and requested domain names to an external certificate authority.

Content

No source excerpt is available for this finding.

The cert-manager installation command lacks a cluster-impact warning.

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The prerequisite instructs applying a remote cert-manager installation manifest directly to the active Kubernetes cluster. It does not warn that this installs or updates cluster-wide resources, including CRDs, controllers, webhooks, and RBAC, rather than merely checking a prerequisite.

Content

No source excerpt is available for this finding.