# CVE-2023-3433: Local Denial of Service in Jami

> A local attacker can cause a denial of service in Jami by inserting special characters into the nickname field, preventing signature creation.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2023
- **Updated:** 22 Oct 2024
- **Also known as:** GHSA-fp7q-45w4-8pv6

## What is CVE-2023-3433?

CVE-2023-3433 is a medium-severity denial of service vulnerability in Savoir-faire Linux Jami, published on 14 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The "nickname" field within Savoir-faire Linux's Jami application is susceptible to a failed state when a user inserts special characters into the field. When present, these special characters, make it so the application cannot create the signature for the user and results in a local denial of service to the application.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-3433?

It affects 1 product.


Products: Savoirfairelinux Jami.

## How do I fix CVE-2023-3433?

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

## Is CVE-2023-3433 being exploited?

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

## Other vulnerabilities in Savoir-faire Linux Jami

- [CVE-2023-3434](https://insights.sbomify.com/CVE-2023-3434/): QRC Handler without Input Validation in Jami (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3433 and fix it if it is affected.

What it is: CVE-2023-3433 is a medium-severity denial of service vulnerability in Savoir-faire Linux Jami, published on 14 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3433 in the wild and no public exploit code.

Affected product: Savoir-faire Linux Jami. 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-2023-3433/ (Markdown: https://insights.sbomify.com/CVE-2023-3433/index.md)
```

## Sources

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

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