# CVE-2017-5592: Other in n/a

> Remote attackers can impersonate users in the XMPP client display due to incorrect Message Carbons implementation, enabling social engineering.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 9 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5592, GHSA-6c39-xj34-c7cw, UBUNTU-CVE-2017-5592

## What is CVE-2017-5592?

CVE-2017-5592 is a medium-severity vulnerability in n/a, published on 9 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 profanity (0.4.7 - 0.5.0).

Weakness: CWE-346 (Origin Validation Error), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-5592?

It affects 1 product.


Products: Profanity Project Profanity.

## How do I fix CVE-2017-5592?

Upgrade to a fixed version.

## Is CVE-2017-5592 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-40769](https://insights.sbomify.com/CVE-2022-40769/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5592 and fix it if it is affected.

What it is: CVE-2017-5592 is a medium-severity vulnerability in n/a, published on 9 Feb 2017. 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-2017-5592 in the wild and no public exploit code.

Affected product: n/a. 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-2017-5592/ (Markdown: https://insights.sbomify.com/CVE-2017-5592/index.md)
```

## Sources

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

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