T09 · Insecure Skill Coding Practices
- Location
SKILL.md:95- Finding
Plaintext Shared Authentication Key Published in Skill Documentation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:95
Vulnerability Type: Hardcoded shared credential
Risk Level: MediumVulnerable Code Snippet:
text v19-e5d585e28439decc614f09f91c4caa8cTechnical Analysis
The document publishes a static value intended for use in the
X-Governance-Keyauthentication header. Although it is presented as a public demonstration key, the audited file does not define an expiration time, endpoint restrictions, rate limits, environment isolation, or authorization scope.A shared static credential cannot reliably identify individual callers and is available to anyone who can read or redistribute the Skill. If a deployed governance service accepts this value, possession of the Skill is sufficient to impersonate other users of the same credential. The API implementation was not included in the project, so whether the key remains active and what permissions it grants could not be verified.
Attack Path
- An attacker obtains
SKILL.mdfrom the Skill package. - The attacker extracts the published key.
- The attacker identifies a deployed governance API that accepts
X-Governance-Key. - The attacker sends requests with the published value in that header.
- If the key is active, the service processes requests under the shared credential's permissions, without reliable per-user attribution.
Impact Assessment
The maximum impact depends on the server-side privileges assigned to the key. Potential impact includes unauthorized access to governance queries, constitution validation, bootstrap status, attention status, stability history, or audit records exposed to that credential.
If the key can access mutation-capable or sensitive endpoints, its publication could also permit unauthorized operations or disclosure of governance data. The repository does not contain the service implementation or authorization policy, so elevated privileges cannot be confirmed.
- An attacker obtains
- Remediation
View remediation
Remediation Suggestions
- Remove the shared key from the distributed Skill and immediately revoke or rotate it if it has ever been accepted by a deployed service.
- Issue unique, short-lived credentials through an authenticated enrollment process.
- Store credentials in an approved secret manager or runtime environment variable rather than documentation or source-controlled files.
- Restrict demonstration credentials to an isolated sandbox with no production data or mutation privileges.
- Apply explicit endpoint scopes, expiration, rate limits, quotas, and source restrictions.
- Record activity against unique identities rather than a shared principal.
- Add automated secret scanning and credential-revocation procedures to the publication workflow.
