CVE-2017-5602 json
An incorrect implementation of "XEP-0280: Message Carbons" in multiple XMPP clients allows a remote attacker to impersonate any user, inclu…
published 2017-02-09 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-14701
- cvss
- 5.9
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
An incorrect implementation of "XEP-0280: Message Carbons" in multiple XMPP clients allows a remote attacker to impersonate any user, including contacts, in the vulnerable application's display. This allows for various kinds of social engineering attacks. This CVE is for jappix 1.0.0 to 1.1.6.
Patch / fix
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- openwall.com http://openwall.com/lists/oss-security/2017/02/09/29 referenced PoC, tagged "exploit" by a source, unverified
- rt-solutions.de https://rt-solutions.de/en/2017/02/CVE-2017-5589_xmpp_carbons/ referenced PoC, tagged "exploit" by a source, unverified
- rt-solutions.de https://rt-solutions.de/wp-content/uploads/2017/02/CVE-2017-5589_xmpp_carbons.pdf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
References
-
github.com
/jappix/jappix/commit/ea6de7c65b80880bdf85df47c1a8a5d3d68491af
patch
-
openwall.com
/lists/oss-security/2017/02/09/29
exploit, mailing-list, third-party-advisory
-
rt-solutions.de
/en/2017/02/CVE-2017-5589_xmpp_carbons/
exploit, technical-description, third-party-advisory
-
rt-solutions.de
/wp-content/uploads/2017/02/CVE-2017-5589_xmpp_carbons.pdf
exploit, technical-description, third-party-advisory
-
securityfocus.com
/bid/96176
vdb-entry
Sources
- CVE List CVE-2017-5602
- NVD CVE-2017-5602
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.