Heym before 0.0.53 fails to verify the X-Telegram-Bot-Api-Secret-Token header on Telegram webhook endpoints when credential_id is absent or secret_token is empty. Remote unauthenticated attackers can post forged Telegram updates to trigger workflows with the owner's configured credentials and execute actions on attacker-supplied input.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products
heymrun:heym
References 3
https://github.com/heymrun/heym/security/advisories/GHSA-pm6h-x3h5-j38h
GitHub Security Advisory (GHSA-pm6h-x3h5-j38h)
https://github.com/heymrun/heym/commit/341d1012367cd74f85c617e1c98dd49e3fcb5e83
Patch Commit
https://www.vulncheck.com/advisories/heym-before-0.0.53-authentication-bypass-v…
VulnCheck Advisory: Heym before 0.0.53 Authentication Bypass via Telegram Webhook