Bluehood monitors local bluetooth activity. Prior to version 0.7.1, when auth_enabled is set in Bluehood, only the HTML page handlers enforced session validation. The /api/* handlers (settings, devices, groups, per-device endpoints including /api/device/{mac}/notes) called no auth check at all.
A network attacker reachable on the dashboard port could read Bluetooth tracking data and modify application state — including the heartbeat URL, prune retention, device groups, and per-device notes — without a session cookie. This issue has been patched in version 0.7.1.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products
dannymcc:bluehood
References 3
https://github.com/dannymcc/bluehood/commit/401479938c0deb1f6f6847d442f98a2d03e…
security-advisories@github.com
https://github.com/dannymcc/bluehood/releases/tag/v0.7.1
security-advisories@github.com
https://github.com/dannymcc/bluehood/security/advisories/GHSA-qj2j-wcg3-74jw
security-advisories@github.com