# CVE-2022-23764: TERUTEN WebCube update remote code execution vulnerability

> Remote attackers can bypass file verification during updates to execute arbitrary code on TERUTEN WebCube servers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-34pp-49c4-xqcp

## What is CVE-2022-23764?

CVE-2022-23764 is a high-severity code injection vulnerability in TERUTEN Co.,Ltd WebCube, published on 17 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The vulnerability causing from insufficient verification procedures for downloaded files during WebCube update. Remote attackers can bypass this verification logic to update both digitally signed and unauthorized files, enabling remote code execution.

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Teruten Webcube.

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

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

## Is CVE-2022-23764 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23764 is a high-severity code injection vulnerability in TERUTEN Co.,Ltd WebCube, published on 17 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23764 in the wild and no public exploit code.

Affected product: TERUTEN Co.,Ltd WebCube. 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-23764/ (Markdown: https://insights.sbomify.com/CVE-2022-23764/index.md)
```

## Sources

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

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