CVE-2022-45197: Slixmpp before 1.8.3 lacks SSL Certificate hostname validation in XMLStream, allowing an attacker to pose as a
CVE-2022-45197 is a high-severity flaw (CVSS 7.5) affecting slixmpp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Slixmpp before 1.8.3 lacks SSL Certificate hostname validation in XMLStream, allowing an attacker to pose as any server in the eyes of Slixmpp.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.5% (top 56%) |
| CISA exploited list | No |
| Weakness | CWE-295 |
| Published | 2022-12-25 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-45197?
slixmpp: upgrade to 1.8.3. Exact commands for each OS are on this page.
Is CVE-2022-45197 being exploited?
CVE-2022-45197 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-45197 affect?
CVE-2022-45197 affects slixmpp. Severity is high (CVSS 7.5). Slixmpp before 1.8.3 lacks SSL Certificate hostname validation in XMLStream, allowing an attacker to pose as any server in the eyes of Slixmpp.
How urgent is CVE-2022-45197?
Priority 42/100. High severity; Remotely exploitable, no login, no user action