# CVE-2023-39983: MXsecurity Register Database Pollution


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Sep 2023
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-5r9f-76wq-x3p4

## What is CVE-2023-39983?

CVE-2023-39983 is a medium-severity vulnerability in Moxa MXsecurity Series, published on 2 Sep 2023. 

### Official description

A vulnerability that poses a potential risk of polluting the MXsecurity sqlite database and the nsm-web UI has been identified in MXsecurity versions prior to v1.0.1. This vulnerability might allow an unauthenticated remote attacker to register or add devices via the nsm-web application.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources), CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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

It affects 1 product.


Products: Moxa Mxsecurity.

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

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

## Is CVE-2023-39983 being exploited?

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

## Other vulnerabilities in Moxa MXsecurity Series

- [CVE-2023-39979](https://insights.sbomify.com/CVE-2023-39979/): MXsecurity Authentication Bypass (critical 9.8)
- [CVE-2023-33236](https://insights.sbomify.com/CVE-2023-33236/): MXsecurity Hardcoded Credential Vulnerability (critical 9.8)
- [CVE-2023-39981](https://insights.sbomify.com/CVE-2023-39981/): MXsecurity Device Information Disclosure (high 7.5)
- [CVE-2023-39982](https://insights.sbomify.com/CVE-2023-39982/): MXsecurity Hardcoded Credential (high 7.5)
- [CVE-2023-33235](https://insights.sbomify.com/CVE-2023-33235/): MXsecurity Command Injection Vulnerability (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39983 is a medium-severity vulnerability in Moxa MXsecurity Series, published on 2 Sep 2023. 
Exploitation: There is no known exploitation of CVE-2023-39983 in the wild and no public exploit code.

Affected product: Moxa MXsecurity Series. 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-39983/ (Markdown: https://insights.sbomify.com/CVE-2023-39983/index.md)
```

## Sources

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

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