# CVE-2023-42425: Other in n/a

> Remote attackers can execute arbitrary code and access sensitive information on Turing Edge+ EVC5FD devices via cloud connection components.

- **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:** 31 Oct 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-pcqh-qfj4-8h2g

## What is CVE-2023-42425?

CVE-2023-42425 is a critical vulnerability in n/a, published on 31 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Turing Video Turing Edge+ EVC5FD v.1.38.6 allows remote attacker to execute arbitrary code and obtain sensitive information via the cloud connection components.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Turing Edge\+ Evc5fd Firmware.

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

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

## Is CVE-2023-42425 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42425 is a critical vulnerability in n/a, published on 31 Oct 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-2023-42425 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-2023-42425/ (Markdown: https://insights.sbomify.com/CVE-2023-42425/index.md)
```

## Sources

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

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