# CVE-2022-43550: Command injection in https://github.com/jitsi

> Attackers can execute arbitrary commands on Windows systems by injecting malicious URLs into Jitsi browser launch operations.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-3r45-9m8q-2cch

## What is CVE-2022-43550?

CVE-2022-43550 is a critical command injection vulnerability in https://github.com/jitsi, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A command injection vulnerability exists in Jitsi before commit 8aa7be58522f4264078d54752aae5483bfd854b2 when launching browsers on Windows which could allow an attacker to insert an arbitrary URL which opens up the opportunity to remote execution.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2022-43550?

It affects 1 product.


Products: Jitsi Jitsi.

## How do I fix CVE-2022-43550?

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

## Is CVE-2022-43550 being exploited?

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

## Other vulnerabilities in https://github.com/jitsi

- [CVE-2022-36736](https://insights.sbomify.com/CVE-2022-36736/): Cross-site request forgery in n/a (medium 6.1)
- [CVE-2017-5603](https://insights.sbomify.com/CVE-2017-5603/): Other in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43550 and fix it if it is affected.

What it is: CVE-2022-43550 is a critical command injection vulnerability in https://github.com/jitsi, published on 9 Feb 2023. 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-2022-43550 in the wild and no public exploit code.

Affected product: https://github.com/jitsi. 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-2022-43550/ (Markdown: https://insights.sbomify.com/CVE-2022-43550/index.md)
```

## Sources

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

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