CVE-2022-20917 [Medium] | Security Vulnerability in Jabber

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.17%	0.89%	+0.72%
2	2025-03-30	0.32%	0.17%	-0.14%
3	2025-03-29	—	0.32%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.17%

0.89%

+0.72%

2025-03-30

0.32%

0.17%

-0.14%

2025-03-29

—

0.32%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.8	1.4	[email protected]
4.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.8	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.8

1.4

[email protected]

4.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.8

1.4

[email protected]

Affected software / configurations for CVE-2022-20917

Vendor	Product	Version	Raw CPE
cisco	jabber	< 12.6.6	cpe:2.3:a:cisco:jabber::::::windows::*
cisco	jabber	< 12.8.8	cpe:2.3:a:cisco:jabber::::::macos::*
cisco	jabber	< 14.1.4	cpe:2.3:a:cisco:jabber::::::android::*
cisco	jabber	< 14.1.4	cpe:2.3:a:cisco:jabber::::::iphone_os::*
cisco	jabber	>= 12.7, < 12.7.6	cpe:2.3:a:cisco:jabber::::::windows::*
cisco	jabber	>= 12.8, < 12.8.7	cpe:2.3:a:cisco:jabber::::::windows::*
cisco	jabber	>= 12.9, < 12.9.7	cpe:2.3:a:cisco:jabber::::::windows::*
cisco	jabber	>= 12.9, < 12.9.8	cpe:2.3:a:cisco:jabber::::::macos::*
cisco	jabber	>= 14.0, < 14.0.5	cpe:2.3:a:cisco:jabber::::::macos::*
cisco	jabber	>= 14.0, < 14.0.5	cpe:2.3:a:cisco:jabber::::::windows::*
cisco	jabber	>= 14.1, < 14.1.3	cpe:2.3:a:cisco:jabber::::::macos::*
cisco	jabber	>= 14.1, < 14.1.3	cpe:2.3:a:cisco:jabber::::::windows::*

References for CVE-2022-20917

URL	Tags
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-jabber-xmpp-Ne9SCM	Vendor Advisory

URL

CVE-2022-20917

Exploit prediction scoring system (EPSS) score for CVE-2022-20917

Common vulnerability scoring system (CVSS) metrics for CVE-2022-20917

Weakness enumeration for CVE-2022-20917

Affected software / configurations for CVE-2022-20917

References for CVE-2022-20917