# CVE-2019-10724: Privilege escalation in n/a

> A low-privileged user can terminate arbitrary high-privilege processes via the Dolby DAX2 API, leading to potential privilege escalation or denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 28 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ffjr-qvmv-p6h7

## What is CVE-2019-10724?

CVE-2019-10724 is a medium-severity vulnerability in n/a, published on 28 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

There is a vulnerability with the Dolby DAX2 API system services in which a low-privileged user can terminate arbitrary processes that are running at a higher privilege. The following are affected products and versions: Legion Y520T_Z370 6.0.1.8642, AIO310-20IAP 6.0.1.8642, AIO510-22ISH 6.0.1.8642, AIO510-23ISH 6.0.1.8642, AIO520-22IKL 6.0.1.8642, AIO520-22IKU 6.0.1.8642, AIO520-24IKL 6.0.1.8642, AIO520-24IKU 6.0.1.8642, AIO520-27IKL 6.0.1.8642, AIO720-24IKB 6.0.1.8642, IdeaCentre 520S-23IKU 6.0.1.8642, ThinkCentre M700z 6.0.1.8642, ThinkCentre M800z 6.0.1.8642, ThinkCentre M810z 6.0.1.8642, ThinkCentre M818z 6.0.1.8642, ThinkCentre M900Z 6.0.1.8642, ThinkCentre M910z 6.0.1.8642, V410z(YT S4250) 6.0.1.8642, 330-14IKBR Win10:6.0.1.8652, 330-15IKBR Win10:6.0.1.8652, 330-15IKBR (Brazil) Win10:6.0.1.8652, 330-15IKBR Touch Win10:6.0.1.8652, 330-17IKBR Win10:6.0.1.8652, YOGA 730-13IKB Win10:6.0.1.8644, YOGA 730-15IKB Win10:6.0.1.8644, ThinkPad L560 6.0.1.8644 and 6.0.1.8652, ThinkPad L570 6.0.1.8644 and 6.0.1.8652, ThinkPad P50 6.0.1.8642, ThinkPad P50s 6.0.1.8642, ThinkPad P51s (20Jx, 20Kx) 6.0.1.8642, ThinkPad P51s (20Hx) 6.0.1.8642, ThinkPad P52s 6.0.1.8642, ThinkPad P70 6.0.1.8642, ThinkPad T25 6.0.1.8642, ThinkPad T460s 6.0.1.8642, ThinkPad T470 6.0.1.8642, ThinkPad T470s 6.0.1.8642, ThinkPad T480 6.0.1.8642, ThinkPad T480s 6.0.1.8642, ThinkPad T560 6.0.1.8642, ThinkPad T570 6.0.1.8642, ThinkPad T580 6.0.1.8642, ThinkPad X1 Carbon 8.66.76.72 and 8.66.68.54, ThinkPad X1 Carbon 6th 6.0.1.8642, ThinkPad X1 Carbon, X1 Yoga 8.66.62.92 and 8.66.62.54, ThinkPad X1 Tablet (20Gx) 6.0.1.8642, ThinkPad X1 Tablet (20Jx) 6.0.1.8642, ThinkPad X1 Tablet Gen 3 6.0.1.8642, ThinkPad X1 Yoga (20Jx) 8.66.88.60, ThinkPad X1 Yoga 3rd 6.0.1.8642, ThinkPad X280 6.0.1.8642, ThinkPad Yoga 260, S1 8.66.62.92 and 8.66.62.54.

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

It affects 108 products.


Products: Lenovo 100e 2nd Gen Firmware, Lenovo 300e 2nd Gen Firmware, Lenovo 330-14ikbr Firmware, Lenovo 330-15ikbr Firmware, Lenovo 330-15ikbr Touch Firmware, Lenovo 330-17ikbr Firmware, Lenovo 720s-15ikb Firmware, Lenovo 720s Touch-15ikb Firmware, Lenovo Aio310-20iap Firmware, Lenovo Aio510-22ish Firmware, Lenovo Aio510-23ish Firmware, Lenovo Aio520-22ikl Firmware, Lenovo Aio520-22iku Firmware, Lenovo Aio520-24ikl Firmware, Lenovo Aio520-24iku Firmware, Lenovo Aio520-27ikl Firmware, Lenovo Aio720-24ikb Firmware, Lenovo B330-15ikbr Firmware, Lenovo E43-80 Firmware, Lenovo E53-80 Firmware and 88 more.

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

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

## Is CVE-2019-10724 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-1892](https://insights.sbomify.com/CVE-2022-1892/): Memory corruption in BIOS (medium 6.7)
- [CVE-2021-3614](https://insights.sbomify.com/CVE-2021-3614/): Privilege escalation in Notebook BIOS (medium 6.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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