# CVE-2022-38625: File upload in n/a

> Authenticated attackers can upload custom firmware to Patlite NH-FB devices due to insufficient validation, enabling malicious code injection.

- **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:** 29 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-89rj-8fq7-2vrc

## What is CVE-2022-38625?

CVE-2022-38625 is a high-severity vulnerability in n/a, published on 29 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Patlite NH-FB v1.46 and below was discovered to contain insufficient firmware validation during the upgrade firmware file upload process. This vulnerability allows authenticated attackers to create and upload their own custom-built firmware and inject malicious code. NOTE: the vendor's position is that this is a design choice, not a vulnerability

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

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

It affects 3 products.


Products: Patlite Nbm-D88n Firmware, Patlite Nhl-3fb1 Firmware, Patlite Nhl-3fv1n Firmware.

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

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

## Is CVE-2022-38625 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18473](https://insights.sbomify.com/CVE-2018-18473/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38625 is a high-severity vulnerability in n/a, published on 29 Aug 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-38625 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-2022-38625/ (Markdown: https://insights.sbomify.com/CVE-2022-38625/index.md)
```

## Sources

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

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