# CVE-2022-48221: Race condition in n/a

> A race condition in the Acuant AcuFill SDK installer allows standard users to overwrite executables, leading to SYSTEM code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:** 4 Apr 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-699h-74gf-wcvm

## What is CVE-2022-48221?

CVE-2022-48221 is a high-severity vulnerability in n/a, published on 4 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Acuant AcuFill SDK before 10.22.02.03. Multiple MSI's get executed out of a standard-user writable directory. Through a race condition and OpLock manipulation, these files can be overwritten by a standard user. They then get executed by the elevated installer. This gives a standard user full SYSTEM code execution (elevation of privileges).

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


Products: Gbgplc Acuant Acufill Sdk.

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

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

## Is CVE-2022-48221 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-48226](https://insights.sbomify.com/CVE-2022-48226/): Privilege escalation in n/a (high 8.4)
- [CVE-2022-48222](https://insights.sbomify.com/CVE-2022-48222/): Privilege escalation in n/a (high 7.8)
- [CVE-2022-48224](https://insights.sbomify.com/CVE-2022-48224/): Privilege escalation in n/a (high 7.3)
- [CVE-2022-48225](https://insights.sbomify.com/CVE-2022-48225/): Privilege escalation in n/a (high 7.3)
- [CVE-2022-48223](https://insights.sbomify.com/CVE-2022-48223/): Other in n/a (medium 6.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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