T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:35- Finding
Unrestricted Exposure of Sensitive Network Request Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 35
Vulnerability Type: Sensitive network data access without documented redaction or authorization controls
Risk Level: MediumVulnerable Code Snippet:
markdown - `view_network_request_details` - Get all details of a specific network request. Returns headers, body, and other metadata for a given request. Use this tool after `view_network_logs` to inspect a specific request in detail. Accepts a `requestId` parameter.Technical Analysis
The documented tool returns all headers, body content, and metadata associated with a selected network request. These fields may contain bearer tokens, session cookies, API keys, personal information, passwords, or confidential application payloads.
The skill does not document default redaction, field-level filtering, request-scope restrictions, user confirmation, or access controls for unredacted content. This conflicts with least-privilege principles because routine network debugging generally does not require disclosing every sensitive field to the agent.
This finding is limited to the capability and missing safeguards described in
SKILL.md. The audited package contains no implementation code demonstrating whether the underlying MCP server applies protections outside this documentation.Attack Path
- The agent invokes
view_network_logsto enumerate requests generated by the application. - The returned list provides an identifier for a request involving authentication or confidential application data.
- The agent passes that identifier to
view_network_request_details. - The tool returns the complete request headers, body, and metadata.
- Sensitive values become available in the agent context and may subsequently be included in generated responses, logs, or retained conversation history.
Impact Assessment
Successful exploitation or accidental misuse could expose authentication toke ...[truncated 548 chars]
- The agent invokes
- Remediation
View remediation
Remediation Suggestions
- Redact sensitive headers by default, including
Authorization,Cookie,Set-Cookie, proxy credentials, API keys, and vendor-specific authentication headers. - Recursively mask sensitive body fields such as passwords, tokens, secrets, payment details, and personally identifiable information.
- Return only metadata and sanitized previews unless the user explicitly authorizes access to an identified request.
- Require separate, informed confirmation before revealing unredacted request content, clearly identifying the request and the types of sensitive data that may be exposed.
- Restrict request-detail access to the active project, application, and debugging session.
- Apply output-size limits and allow field-level selection so agents retrieve only the information necessary for diagnosis.
- Prevent unredacted values from being written to persistent logs or telemetry, and document retention and deletion behavior.
- Add automated tests verifying that common credentials and sensitive body fields are consistently masked.
- Update
SKILL.mdto explain the redaction policy, authorization process, access boundaries, and safe handling requirements.
- Redact sensitive headers by default, including
