T05 · Unauthorized Access and Privilege Escalation
- Location
.idea/claudeCodeTabState.xml:9- Finding
Claude IDE Session Configured to Bypass Permission Prompts
- Content
View full analysis
Vulnerability Details
File Location:
.idea/claudeCodeTabState.xml, lines 9–14
Vulnerability Type: Agent permission bypass
Risk Level: HighVulnerable Code
xml <option name="provider" value="claude" /> <option name="sessionId" value="123b0254-63e1-4720-b9ee-981970abcdd4" /> <option name="cwd" value="$PROJECT_DIR$" /> <option name="model" value="claude-opus-4-6" /> <option name="permissionMode" value="bypassPermissions" /> <option name="reasoningEffort" value="medium" />Technical Analysis
The repository contains committed Claude IDE plugin session state that sets
permissionModetobypassPermissions. If a compatible plugin imports or restores this configuration, Agent tool operations may execute without the normal user-approval prompts.This setting violates least-privilege principles because the project is a documentation-only stock-analysis Skill. Its legitimate functionality does not require unrestricted filesystem, command-execution, or network permissions.
The setting is not itself an executable payload, and the audited project contains no destructive command that directly exploits it. Nevertheless, it weakens an important security boundary and can amplify the effect of erroneous instructions, prompt injection, or malicious content added later.
Attack Path
- A user obtains the project and opens it in an IDE with a compatible Claude integration.
- The integration reads or restores the committed session configuration from
.idea/claudeCodeTabState.xml. - The integration applies
permissionMode="bypassPermissions". - The user invokes the Agent or loads instructions that cause tool use.
- Tool operations may proceed without the normal approval prompts, reducing the user's opportunity to reject unsafe filesystem, command, or network actions.
Successful exploitation depends on the IDE integration honoring the committed state and on instructions or content causing a privileged tool action.
Impact Assessme
...[truncated 671 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
.idea/claudeCodeTabState.xmlfrom the distributed project and version-control history where practical. - Add
.idea/claudeCodeTabState.xml, or the entire.idea/directory when shared IDE settings are unnecessary, to.gitignore. - Reset the Claude integration to its normal or approval-required permission mode.
- Require explicit user confirmation for command execution, filesystem modification, external network access, and access outside the project directory.
- Do not commit Agent session identifiers or other user-specific plugin state.
- Document the minimum permissions required by the Skill and validate imported IDE configurations against that baseline.
- Add a repository check that rejects committed Agent configurations containing values such as
bypassPermissions.
- Remove
