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

> Attackers can execute arbitrary commands on Hanwha IP cameras via the NAS storage test function due to improper input sanitization.

- **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:** 23 May 2023
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-5xjw-8r97-6fj2

## What is CVE-2023-31996?

CVE-2023-31996 is a high-severity command injection vulnerability in n/a, published on 23 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hanwha IP Camera ANE-L7012R 1.41.01 is vulnerable to Command Injection due to improper sanitization of special characters for the NAS storage test function.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 118 products.


Products: Hanwhavision Ane-L6012r Firmware, Hanwhavision Ane-L7012r Firmware, Hanwhavision Ano-L6012r Firmware, Hanwhavision Ano-L6022r Firmware, Hanwhavision Ano-L6082r Firmware, Hanwhavision Ano-L7012r Firmware, Hanwhavision Ano-L7022r Firmware, Hanwhavision Ano-L7082r Firmware, Hanwhavision Anv-L6012r Firmware, Hanwhavision Anv-L6023r Firmware, Hanwhavision Anv-L6082r Firmware, Hanwhavision Anv-L7012r Firmware, Hanwhavision Anv-L7082r Firmware, Hanwhavision Pnm-12082rvd Firmware, Hanwhavision Pnm-7002vd Firmware, Hanwhavision Pnm-7082rvd Firmware, Hanwhavision Pnm-8082vt Firmware, Hanwhavision Pnm-9000qb Firmware, Hanwhavision Pnm-9000vd Firmware, Hanwhavision Pnm-9002vq Firmware and 98 more.

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

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

## Is CVE-2023-31996 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-5038](https://insights.sbomify.com/CVE-2023-5038/): Unauthenticated DoS (high 8.7)
- [CVE-2023-5037](https://insights.sbomify.com/CVE-2023-5037/): Authenticated Command Injection (high 7.1)
- [CVE-2023-31995](https://insights.sbomify.com/CVE-2023-31995/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2023-31994](https://insights.sbomify.com/CVE-2023-31994/): Denial of service in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31996 is a high-severity command injection vulnerability in n/a, published on 23 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31996 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-31996/ (Markdown: https://insights.sbomify.com/CVE-2023-31996/index.md)
```

## Sources

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

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