# CVE-2023-51073: Command injection in n/a

> Remote attackers can execute arbitrary code on Buffalo LS210D NAS devices via the firmware update script.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 11 Jan 2024
- **Updated:** 6 Jun 2025
- **Also known as:** GHSA-8223-5qc2-w3gf

## What is CVE-2023-51073?

CVE-2023-51073 is a high-severity command injection vulnerability in n/a, published on 11 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Buffalo LS210D v.1.78-0.03 allows a remote attacker to execute arbitrary code via the Firmware Update Script at /etc/init.d/update_notifications.sh.

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

It affects 1 product.


Products: Buffalo Ls210d Firmware.

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

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

## Is CVE-2023-51073 being exploited?

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

Public exploit code:

- Firmware Update Server Verification Vulnerability on Buffalo LS210D Version 1.78-0.03 (github_poc): https://github.com/christopher-pace/CVE-2023-51073

## Other vulnerabilities in n/a

- [CVE-2023-49038](https://insights.sbomify.com/CVE-2023-49038/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51073 is a high-severity command injection vulnerability in n/a, published on 11 Jan 2024. 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-51073 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-51073/ (Markdown: https://insights.sbomify.com/CVE-2023-51073/index.md)
```

## Sources

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

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