# CVE-2023-52972: Security feature bypass in YutuFZ-5651S1

> Low-privilege users can bypass SDDL permission checks to terminate system processes on Huawei PCs, causing denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-5vgw-4mhf-xvgm

## What is CVE-2023-52972?

CVE-2023-52972 is a medium-severity vulnerability in Huawei YutuFZ-5651S1, published on 26 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei PCs have a vulnerability that allows low-privilege users to bypass SDDL permission checks . Successful exploitation this vulnerability could lead to termination of some system processes.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Huawei Yutufz-5651s1 Senaryaudio.

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

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

## Is CVE-2023-52972 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52972 is a medium-severity vulnerability in Huawei YutuFZ-5651S1, published on 26 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52972 in the wild and no public exploit code.

Affected product: Huawei YutuFZ-5651S1. 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-52972/ (Markdown: https://insights.sbomify.com/CVE-2023-52972/index.md)
```

## Sources

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

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