MuseBot before 2.0.0 Authentication Bypass via Hard-Coded Session Key

Summary

MuseBot before 2.0.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to forge admin sessions by using the hard-coded default session_key 'muse_bot_session_key'. Attackers can sign a MuseBot-session cookie carrying a user_id to gain full administrative access, reading password hashes, chat records, and bot configuration, and stopping bots.

Remediation

1. Inventory every yincongcyincong MuseBot deployment, including staging.
2. Upgrade yincongcyincong MuseBot to 2.0.0.
3. Confirm the running version after the upgrade.

References

• Patchhttps://github.com/yincongcyincong/MuseBot/commit/139f6158b50283b983d76976f593a3a09a064681
• Patchhttps://github.com/yincongcyincong/MuseBot/commit/3e64518948fe7037058f07ef987d35216c3f0cae
• Advisoryhttps://hackmd.io/@hieuPenguinnn/musebot-admin-default-session-key-auth-bypass
• Advisoryhttps://www.vulncheck.com/advisories/musebot-before-2.0.0-authentication-bypass-via-hard-coded-session-key
• Referencehttps://github.com/yincongcyincong/MuseBot
• Referencehttps://github.com/yincongcyincong/MuseBot/blob/v1.0.42/admin/conf/conf.go#L28
• Referencehttps://github.com/yincongcyincong/MuseBot/blob/v1.0.42/admin/controller/login.go#L19-L88
• Referencehttps://github.com/yincongcyincong/MuseBot/issues/61