Описание
Improper Validation of Certificate with Host Mismatch in mellium.im/xmpp/websocket
Impact
If no TLS configuration is provided by the user, the websocket package constructs its own TLS configuration using recommended defaults. When looking up a WSS endpoint using the DNS TXT record method described in XEP-0156: Discovering Alternative XMPP Connection Methods the ServerName field was incorrectly being set to the name of the server returned by the TXT record request, not the name of the initial server we were attempting to connect to. This means that any attacker that can spoof a DNS record (ie. in the absence of DNSSEC, DNS-over-TLS, DNS-over-HTTPS, or similar technologies) could redirect the user to a server of their choosing and as long as it had a valid TLS certificate for itself the connection would succeed, resulting in a MITM situation.
Patches
All users should upgrade to v0.21.1.
Workarounds
To work around the issue, manually specify a TLS configuration with the correct hostname.
References
For more information
If you have any questions or comments about this advisory:
- Reach out on XMPP to sam@samwhited.com
- Email us at sam@samwhited.com
Ссылки
- https://github.com/mellium/xmpp/security/advisories/GHSA-h289-x5wc-xcv8
- https://nvd.nist.gov/vuln/detail/CVE-2022-24968
- https://github.com/mellium/xmpp/pull/260
- https://github.com/mellium/xmpp/commit/0d92aa486da69b71f2f4a30e62aa722c711b98ac
- https://mellium.im/cve/cve-2022-24968
- https://mellium.im/issue/259
- https://pkg.go.dev/vuln/GO-2022-0370
Пакеты
mellium.im/xmpp
>= 0.18.0, < 0.21.1
0.21.1
Связанные уязвимости
In Mellium mellium.im/xmpp through 0.21.0, an attacker capable of spoofing DNS TXT records can redirect a WebSocket connection request to a server under their control without causing TLS certificate verification to fail. This occurs because the wrong host name is selected during this verification.