Credential Access
- Category
- Privilege Escalation
- Confidence
- 90% confidence
- Finding
The documented flow has the agent operate directly on a highly sensitive credential file and determine an authorized reader program, which can alter access control around the secret. If the agent selects the wrong binary, authorizes an attacker-controlled wrapper, or protects the wrong file, the result could deny legitimate access or unintentionally grant access to secrets.
- Content
md You: Please protect ~/.ssh/id_rsa Agent: I'll protect your SSH private key. 1. Credential file: ~/.ssh/id_rsa 2. Authorized program: /usr/bin/ssh (used by git over ssh) 3. Protecting (SHA256 measured, max 2 opens per PID): $ credctl protect --strategy BASIC \
