Executive Summary

Hermes Agent versions before 0.16.0 create two files, response_store.db and webhook_subscriptions.json, with world-readable permissions (mode 0o644). This means that any local user on the system can read these files.

These files contain sensitive information such as conversation history, tool payloads, prompts, and per-route HMAC secrets. Because the files are accessible to all local users, attackers with local filesystem access can directly read these files and obtain this sensitive data.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive information stored by Hermes Agent. Local attackers can access conversation histories, tool payloads, prompts, and HMAC secrets by reading the exposed files.

Such exposure can compromise the confidentiality of communications and potentially allow attackers to misuse HMAC secrets to impersonate or manipulate routes, leading to further security risks.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves Hermes Agent before version 0.16.0 creating files response_store.db and webhook_subscriptions.json with world-readable permissions (mode 0o644), exposing sensitive data to local users.

To detect this vulnerability on your system, you can check for the existence of these files and their permissions.

• Use the command: ls -l /path/to/hermes_agent/response_store.db
• Use the command: ls -l /path/to/hermes_agent/webhook_subscriptions.json

If these files exist and have permissions set to 644 (world-readable), the system is vulnerable.

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation involves restricting the permissions of the affected files to prevent world-readable access.

• Change the permissions of response_store.db and webhook_subscriptions.json to be readable only by the owner, for example using: chmod 600 /path/to/hermes_agent/response_store.db
• Similarly, run: chmod 600 /path/to/hermes_agent/webhook_subscriptions.json

Additionally, upgrade Hermes Agent to version 0.16.0 or later where this issue is fixed.

Useful 0 Not Useful 0