Blueprint Studio vulnerabilities

Blueprint Studio before version 2.5.2 returns raw exception strings in API responses to authenticated Home Assistant users. Some exception messages may contain internal filesystem paths or implementation details. The disclosed information could help an authenticated user fingerprint a Home Assistant installation and refine follow-up attacks.

Blueprint Studio before version 2.5.2 in the legacy stateless terminal command execution path accepts a cwd working-directory parameter and checks only whether the directory exists, without requiring it to remain inside the Home Assistant configuration directory. An administrator using the restricted terminal helper could select an existing directory outside the intended configuration boundary. Commands could then access or modify host paths permitted by the Home Assistant container and filesystem permissions, weakening the helper's expected filesystem restriction.

Blueprint Studio before version 2.5.2 in terminal SSH key authentication writes SSH private-key material to a file under the Home Assistant configuration directory before applying restrictive permissions and relies on best-effort cleanup. The key could temporarily remain on disk and could persist if cleanup failed or Home Assistant crashed. A user or process with filesystem access to the Home Assistant configuration directory could obtain the residual private key.

Blueprint Studio before version 2.5.2 contains a command injection vulnerability in the Git credential helper, where username and token are interpolated without validation. An attacker who can set Git credentials can inject shell commands, leading to arbitrary command execution with Home Assistant privileges.

Blueprint Studio before version 2.5.2 configured Git's credential.helper store when saving Git credentials, causing Git credential-store to persist usernames and access tokens in plaintext in the .git-credentials file for the user running Home Assistant. Tokens could remain outside Blueprint Studio's intended Home Assistant storage and be read by other users or processes with access to the same filesystem context. The persistent helper configuration also affected later Git operations beyond the immediate Blueprint Studio action.

Blueprint Studio before version 2.5.2 fails to consistently enforce admin-only authorization boundaries, allowing any authenticated user to access admin-intended backend API actions. This includes invoking Home Assistant services, modifying configuration files, accessing streams, and uploading files.