Skip to content

[LOW][Security] Error Messages May Expose Internal Implementation Details #161

@filthyrake

Description

@filthyrake

Summary

Exception messages from underlying libraries (aiohttp, requests) are directly included in API responses. These messages may contain internal paths, hostnames, or stack traces.

Affected Projects

  • pfsense-mcp
  • truenas-mcp
  • proxmox-mcp

Vulnerability Details

An attacker could trigger various error conditions to gather information about the server's internal architecture, library versions, network topology, and potential vulnerabilities.

Example

raise TrueNASAPIError(f"API request failed: {response.status} - {error_text}")

Recommended Fix

  1. Log full exception details server-side
  2. Return generic error messages to clients (e.g., "Connection failed" instead of full exception text)
  3. Implement error code mapping to user-friendly messages

References

  • CWE-209 (Generation of Error Message Containing Sensitive Information)

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    category: securitySecurity-related issueenhancementNew feature or requestpfsense-mcpIssues specific to pfSense MCP serverproxmox-mcpIssues specific to Proxmox MCP serverseverity: lowLow priority issuetruenas-mcpIssues specific to TrueNAS MCP server

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions