# CVE-2023-27748: File upload in n/a

> Attackers can upload malicious firmware to BlackVue dashcams due to missing authenticity checks, enabling arbitrary code execution.

- **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:** 13 Apr 2023
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-9xwc-r37w-mmjm

## What is CVE-2023-27748?

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

### Official description

BlackVue DR750-2CH LTE v.1.012_2022.10.26 does not employ authenticity check for uploaded firmware. This can allow attackers to upload crafted firmware which contains backdoors and enables arbitrary code execution.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 2 products.


Products: Blackvue Dr750-2ch Ir Lte Firmware, Blackvue Dr750-2ch Lte Firmware.

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

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

## Is CVE-2023-27748 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-27746](https://insights.sbomify.com/CVE-2023-27746/): Weak cryptography in n/a (critical 9.8)
- [CVE-2023-27747](https://insights.sbomify.com/CVE-2023-27747/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27748 is a critical vulnerability in n/a, published on 13 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27748 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-27748/ (Markdown: https://insights.sbomify.com/CVE-2023-27748/index.md)
```

## Sources

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

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