🛡️ CVE-2022-45197 on Debian — slixmpp
Description
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.
Distribution advisory
This page covers CVE-2022-45197 as tracked by Debian, for the package slixmpp. The fix is available in version 1.8.3-1; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability none.
Weakness class
DEBIAN-CVE-2022-45197 is classified as CWE-295: Improper Certificate Validation. A TLS certificate is accepted without proper verification, so a man-in-the-middle can present their own.
Affected software
DEBIAN-CVE-2022-45197 is recorded against 1 package.
- slixmpp (fixed in 1.8.3-1)
Timeline and source
Published on 25 December 2022 and last revised on 4 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2022-45197 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| slixmpp | — | 1.8.3-1 |
References
Similar Threats
- High CVE-2022-45197
- Unknown UBUNTU-CVE-2022-45197
- Unknown CVE-2017-5591
- High CVE-2019-1000021
Site Security Check
Is slixmpp part of your stack?
DEBIAN-CVE-2022-45197 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.