# CVE-2022-39212: Last video frame is still sent after video is disabled in a call in Nextcloud Talk

> Attackers can view the last video frame of participants who disabled video but kept a camera selected, exposing sensitive visual data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-wq3g-2x46-q2gv

## What is CVE-2022-39212?

CVE-2022-39212 is a medium-severity vulnerability in nextcloud security-advisories, published on 16 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nextcloud Talk is an open source chat, video & audio calls client for the Nextcloud platform. In affected versions an attacker could see the last video frame of any participant who has video disabled but a camera selected. It is recommended that the Nextcloud Talk app is upgraded to 13.0.8 or 14.0.4. Users unable to upgrade should select "None" as camera before joining the call.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Nextcloud Talk.

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

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

## Is CVE-2022-39212 being exploited?

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

## Other vulnerabilities in nextcloud security-advisories

- [CVE-2020-8180](https://insights.sbomify.com/CVE-2020-8180/): Code injection in Nextcloud Talk (critical 9.9)
- [CVE-2021-32689](https://insights.sbomify.com/CVE-2021-32689/): Nextcloud Talk not properly disassociating users from chats after account deletion (high 8.1)
- [CVE-2023-39957](https://insights.sbomify.com/CVE-2023-39957/): Path traversal allows tricking the Talk Android app into writing files into it's root directory (high 7.2)
- [CVE-2021-32676](https://insights.sbomify.com/CVE-2021-32676/): Session Fixation in Nextcloud Talk (medium 6.5)
- [CVE-2021-39222](https://insights.sbomify.com/CVE-2021-39222/): XSS in Talk (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39212 is a medium-severity vulnerability in nextcloud security-advisories, published on 16 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39212 in the wild and no public exploit code.

Affected product: nextcloud security-advisories. 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-39212/ (Markdown: https://insights.sbomify.com/CVE-2022-39212/index.md)
```

## Sources

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

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