# CVE-2022-4816: Denial of service in Safecenter

> A local user can crash the Lenovo Safecenter application, causing a denial of service.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-h4m9-g4m2-rgjv

## What is CVE-2022-4816?

CVE-2022-4816 is a medium-severity denial of service vulnerability in Lenovo Safecenter, published on 23 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A denial-of-service vulnerability has been identified in Lenovo Safecenter that could allow a local user to crash the application.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2022-4816?

It affects 1 product.


Products: Lenovo Safecenter.

## How do I fix CVE-2022-4816?

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

## Is CVE-2022-4816 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4816 and fix it if it is affected.

What it is: CVE-2022-4816 is a medium-severity denial of service vulnerability in Lenovo Safecenter, published on 23 Jan 2023. 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-2022-4816 in the wild and no public exploit code.

Affected product: Lenovo Safecenter. 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-2022-4816/ (Markdown: https://insights.sbomify.com/CVE-2022-4816/index.md)
```

## Sources

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

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