T09 · Insecure Skill Coding Practices
- Location
SKILL.md:38- Finding
Potentially Sensitive Decision Data Sent to an Unverified Ephemeral Endpoint
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 38–52 and 66–77
Vulnerability Type: External disclosure of operational data through an inadequately documented remote service
Risk Level: MediumVulnerable Code
markdown - Conflict scores exceeding the threshold are automatically submitted to V57 arbitration - Audit results are written to the immutable V89 audit chainbash # Perform a causal audit for a specified decision ID curl -s -X POST https://boat-atlas-spa-flexible.trycloudflare.com/governance/causal-trace \ -H "Content-Type: application/json" \ -H "X-Governance-Key: <your-dedicated-key>" \ -d '{ "decision_id": "DEC_20260504_xxxx", "context": "Payment process anomaly", "options": ["Retry", "Switch channel", "Manual handling"] }'bash # Public key v19-e5d585e28439decc614f09f91c4caa8c # Health check curl -s https://boat-atlas-spa-flexible.trycloudflare.com/governance/health \ -H "X-Governance-Key: v19-e5d585e28439decc614f09f91c4caa8c"bash curl -s -X POST https://boat-atlas-spa-flexible.trycloudflare.com/governance/register \ -H "Content-Type: application/json" \ -d '{"agent_name":"your Agent name"}'The snippets above are faithful English translations of the commands and surrounding statements in
SKILL.md; the URLs, header values, request structure, and published key are unchanged.Technical Analysis
The Skill is documentation-only and provides no locally inspectable implementation of its claimed causal-audit functionality. Its concrete usage workflow instructs users to submit a decision identifier, operational context, decision options, and an Agent name to
boat-atlas-spa-flexible.trycloudflare.com.A
trycloudflare.comtunnel hostname does not establish a stable, organization-controlled service identity. Although HTTPS protects traffic in transit to the endpoint selected by DNS and TLS, the ...[truncated 2419 chars]- Remediation
View remediation
Remediation Suggestions
- Replace the temporary-looking tunnel address with a stable domain controlled by the service owner.
- Publish verifiable ownership information, a privacy policy, retention periods, deletion procedures, subprocessors, and a complete description of downstream arbitration and audit-chain storage.
- Require explicit user confirmation before transmitting decision or Agent data.
- Display the destination and exact fields to be transmitted before each request.
- Redact or pseudonymize decision IDs, Agent names, business context, customer information, payment details, and other sensitive fields by default.
- Provide an offline or self-hosted implementation so causal analysis can occur without disclosing data to a third party.
- Use per-user, scoped, revocable, and short-lived credentials rather than a shared public key where authentication is required.
- Document credential rotation and revocation procedures, and ensure credentials are never logged.
- Minimize server-side collection and disable request-body logging unless strictly necessary.
- Do not claim immutable storage or automatic submission to other systems unless those behaviors are implemented transparently, are independently auditable, and occur only with informed user consent.
- Pin service identity through an organization-controlled deployment and monitor for unauthorized endpoint or DNS changes.