# CVE-2022-20917: Other in Cisco Jabber

> An authenticated remote attacker can manipulate XMPP message content in Cisco Jabber, potentially causing the client to perform unsafe actions.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-qw6v-cqcw-98jc

## What is CVE-2022-20917?

CVE-2022-20917 is a medium-severity vulnerability in Cisco Jabber, published on 15 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the Extensible Messaging and Presence Protocol (XMPP) message processing feature of Cisco Jabber could allow an authenticated, remote attacker to manipulate the content of XMPP messages that are used by the affected application.
 This vulnerability is due to the improper handling of nested XMPP messages within requests that are sent to the Cisco Jabber client software. An attacker could exploit this vulnerability by connecting to an XMPP messaging server and sending crafted XMPP messages to an affected Jabber client. A successful exploit could allow the attacker to manipulate the content of XMPP messages, possibly allowing the attacker to cause the Jabber client application to perform unsafe actions.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Cisco Jabber.

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

No fix has been published for CVE-2022-20917 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-20917 being exploited?

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

## Other vulnerabilities in Cisco Jabber

- [CVE-2021-1411](https://insights.sbomify.com/CVE-2021-1411/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)
- [CVE-2021-1417](https://insights.sbomify.com/CVE-2021-1417/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)
- [CVE-2021-1418](https://insights.sbomify.com/CVE-2021-1418/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)
- [CVE-2021-1469](https://insights.sbomify.com/CVE-2021-1469/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)
- [CVE-2021-1471](https://insights.sbomify.com/CVE-2021-1471/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-20917 is a medium-severity vulnerability in Cisco Jabber, published on 15 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-20917 in the wild and no public exploit code.

Affected product: Cisco Jabber. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-20917/ (Markdown: https://insights.sbomify.com/CVE-2022-20917/index.md)
```

## Sources

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

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