# CVE-2023-43268: Deserialization in n/a

> Attackers can exploit a deserialization flaw in the Deyue Remote Vehicle Management System to potentially execute arbitrary code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 Oct 2023
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-26xj-hxvp-rc79

## What is CVE-2023-43268?

CVE-2023-43268 is a high-severity unsafe deserialization vulnerability in n/a, published on 2 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Deyue Remote Vehicle Management System v1.1 was discovered to contain a deserialization vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Deyue Remote Vehicle Management System Project Deyue Remote Vehicle Management System.

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

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

## Is CVE-2023-43268 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43268 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43268 is a high-severity unsafe deserialization vulnerability in n/a, published on 2 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43268 exists.

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-43268/ (Markdown: https://insights.sbomify.com/CVE-2023-43268/index.md)
```

## Sources

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

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