# CVE-2019-12223: Memory corruption in n/a

> An attacker can cause a denial of service on Hanwha Techwin NVR devices by submitting a long username that triggers a buffer overflow and system reboot.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 5 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fjr3-w9q4-qj56

## What is CVE-2019-12223?

CVE-2019-12223 is a high-severity memory corruption vulnerability in n/a, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in NVR WebViewer on Hanwah Techwin SRN-472s 1.07_190502 devices, and other SRN-x devices before 2019-05-03. A system crash and reboot can be achieved by submitting a long username in excess of 117 characters. The username triggers a buffer overflow in the main process controlling operation of the DVR system, rendering services unavailable during the reboot operation. A repeated attack affects availability as long as the attacker has network access to the device.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2019-12223?

It affects 3 products.


Products: Hanwha-Security Srn-1673s Firmware, Hanwha-Security Srn-472s Firmware, Hanwha-Security Srn-873s Firmware.

## How do I fix CVE-2019-12223?

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

## Is CVE-2019-12223 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12223 and fix it if it is affected.

What it is: CVE-2019-12223 is a high-severity memory corruption vulnerability in n/a, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12223 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-2019-12223/ (Markdown: https://insights.sbomify.com/CVE-2019-12223/index.md)
```

## Sources

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

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