Incorrect Authorization in Plastic Labs Honcho Allows Unauthorized Workspace Data Access

Executive Summary

Plastic Labs Honcho through version 3.3.0 has an authorization flaw where users with peer or session-scoped API keys can access workspace data meant for workspace or admin keys. The vulnerability occurs because the get_or_create_workspace function only checks the workspace claim, allowing attackers to submit a parent workspace name to the POST /v3/workspaces endpoint and retrieve sensitive metadata and configuration like custom_instructions.

Useful 0 Not Useful 0

Detection Guidance

To detect this vulnerability, inspect API requests to the POST /v3/workspaces endpoint. Check if peer- or session-scoped tokens can retrieve workspace metadata like custom_instructions. Use tools like curl to test with different token scopes and verify unauthorized access. Example: curl -H 'Authorization: Bearer <token>' -X POST -H 'Content-Type: application/json' -d '{"name":"<workspace_name>"}' https://api.honcho.dev/v3/workspaces

Monitor logs for unauthorized workspace data access attempts. Verify that workspace-scoped or admin tokens are the only ones permitted to read sensitive workspace configurations.

Useful 0 Not Useful 0

Impact Analysis

If you use Plastic Labs Honcho with API keys that are not workspace or admin-scoped, an attacker could exploit this flaw to read workspace data, including configurations and instructions. This may lead to unauthorized access to sensitive information, data leaks, or misuse of workspace settings.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could violate compliance requirements such as GDPR or HIPAA by allowing unauthorized access to sensitive data. Exposure of workspace configurations or custom instructions may result in data breaches, leading to potential legal penalties, reputational damage, and failure to meet regulatory standards for data protection and access controls.

Useful 0 Not Useful 0

Mitigation Strategies

Update Plastic Labs Honcho to the latest version beyond 3.3.0 to address the authorization flaw. Restrict API key permissions to the minimum required scope and avoid using parent workspace names in API requests. Review and audit all active API keys for potential misuse.

Useful 0 Not Useful 0