T09 · Insecure Skill Coding Practices
- Location
SKILL.md:147- Finding
Certificate Private Keys Are Exposed Through an API Endpoint Without Declared Access Controls
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This certificate-management skill is coherent, but it exposes certificate issuance and private-key download workflows without documented access controls or private-key handling guidance.
Review this carefully before installing. Use it only if you trust the external certificate service and can verify that certificate issuance and downloads require strong authentication, per-domain authorization, and safe private-key handling outside the published OpenAPI contract. Do not let agents download or display private.key unless explicitly needed, and never log, share, or commit downloaded keys.
SKILL.md:147Certificate Private Keys Are Exposed Through an API Endpoint Without Declared Access Controls
The skill explicitly exposes a download endpoint that can return private.key, but the documentation does not warn users that this is highly sensitive key material requiring strict handling. In the context of an SSL certificate manager, omission of such warnings increases the chance that users will download, store, or transmit private keys insecurely, leading to certificate compromise and impersonation of protected domains.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## References
- **Kong Route:** https://api.mkkpro.com/security/ssl-certificate-manager
- **API Docs:** https://api.mkkpro.com:8044/docs
The OpenAPI manifest exposes sensitive certificate-management operations such as DNS challenge generation, certificate issuance, certificate download, and domain debugging without documenting any authentication, authorization, user-consent, or invocation-scope constraints. In an agent setting, this can enable unintended or overly broad use of security-sensitive actions, including certificate issuance workflows and access to certificate artifacts, which raises abuse and misissuance risk.
The natural-language title is presented only in English, and the file provides no indication that users may choose another language or locale. Under the stated policy, forcing a single language without opt-in can be a policy issue when no justification is documented.
No suspicious patterns detected.