Vulnerability in sleekxmpp (CVE-2017-5591)
Summary
Vulnerability in sleekxmpp (CVE-2017-5591). Data can be tampered with by attackers. Mitigation: upgrade to 1.3.2 or later.
Original description
The description as published by the source.
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 SleekXMPP up to 1.3.1 and Slixmpp all versions up to 1.2.3, as bundled in poezio (0.8 - 0.10) and other products.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2017-5591 has been found in sleekxmpp.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade sleekxmpp to 1.3.2 or later.
If unsure, ask your IT team or search "sleekxmpp CVE-2017-5591" on the vendor's site.
CVE-2017-5591 (sleekxmpp) — CWE-20 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.3.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in sleekxmpp.
Check the vendor advisory for the affected versions of sleekxmpp.
Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers.
Update to 1.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sleekxmpp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sleekxmpp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sleekxmppを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sleekxmpp to 1.3.2ステージング環境で 1.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2017-5591 sleekxmpp Fixed in: 1.3.1-6
References
- advisory securityfocus.com
- advisory nvd.nist.gov
- advisory github.com
- package pypi.org
- patch github.com
- report openwall.com
- report rt-solutions.de
- report rt-solutions.de