# CVE-2019-15513: Denial of service in n/a

> A mishandled lock in libuci causes a device hang when processing long SetWanSettings commands, affecting Motorola CX2L and C1 routers.

- **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:** 23 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hwg2-2rxq-2xm4

## What is CVE-2019-15513?

CVE-2019-15513 is a high-severity denial of service vulnerability in n/a, published on 23 Aug 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 OpenWrt libuci (aka Library for the Unified Configuration Interface) before 15.05.1 as used on Motorola CX2L MWR04L 1.01 and C1 MWR03 1.01 devices. /tmp/.uci/network locking is mishandled after reception of a long SetWanSettings command, leading to a device hang.

Weakness: CWE-667 (Improper Locking)

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

It affects 3 products.


Products: Motorola C1 Mwr03 Firmware, Motorola Cx2l Mwr04l Firmware, Openwrt Libuci.

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

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

## Is CVE-2019-15513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15513 is a high-severity denial of service vulnerability in n/a, published on 23 Aug 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-15513 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-15513/ (Markdown: https://insights.sbomify.com/CVE-2019-15513/index.md)
```

## Sources

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

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