# CVE-2022-45197: Slixmpp lacks SSL Certificate hostname validation in XMLStream

> An attacker can bypass SSL certificate hostname validation in Slixmpp, allowing them to impersonate any server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-45197, GHSA-q6cq-m9gm-6q2f, MGASA-2022-0469, PYSEC-2022-43013, UBUNTU-CVE-2022-45197, openSUSE-SU-2022:10241-1, openSUSE-SU-2022:10242-1, openSUSE-SU-2024:12551-1, openSUSE-SU-2025:14628-1

## What is CVE-2022-45197?

CVE-2022-45197 is a high-severity vulnerability in n/a, published on 25 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-45197?

3 open source packages ship an affected version, including slixmpp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `slixmpp` | PyPI | All versions | 1.8.3 |
| `slixmpp` | PyPI | All versions | 1.8.3 |
| `slixmpp` | PyPI | All versions | 1.8.3 |
| `python-slixmpp` | SUSE:Package Hub 15 SP3 | All versions | 1.4.2-bp153.2.3.1 |
| `python-slixmpp` | SUSE:Package Hub 15 SP4 | All versions | 1.4.2-bp154.2.3.1 |
| `python-slixmpp` | openSUSE:Leap 15.3 | All versions | 1.4.2-bp153.2.3.1 |
| `python-slixmpp` | openSUSE:Leap 15.4 | All versions | 1.4.2-bp154.2.3.1 |
| `python-slixmpp` | openSUSE:Tumbleweed | All versions | 1.8.6-1.1 |

Products: Slixmpp Project Slixmpp.

## How do I fix CVE-2022-45197?

Upgrade slixmpp to 1.8.3 or later.

## Is CVE-2022-45197 being exploited?

There is no known exploitation of CVE-2022-45197 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-1000021](https://insights.sbomify.com/CVE-2019-1000021/): slixmpp Incorrect Access Control (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45197 and fix it if it is affected.

What it is: CVE-2022-45197 is a high-severity vulnerability in n/a, published on 25 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45197 in the wild and no public exploit code.

Affected packages and fixed versions:
- slixmpp (PyPI): affected all versions; fixed in 1.8.3
- slixmpp (PyPI): affected all versions; fixed in 1.8.3
- slixmpp (PyPI): affected all versions; fixed in 1.8.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-45197/ (Markdown: https://insights.sbomify.com/CVE-2022-45197/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-45197
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-45197
- OSV: https://osv.dev/vulnerability/CVE-2022-45197

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-45197/
Summaries are generated and may contain mistakes; the official description above is the record.