# CVE-2021-44968: Use after free in n/a

> A use-after-free vulnerability in IOBit Advanced SystemCare allows malicious users to execute arbitrary code or cause a system crash via crafted IOCTL requests.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7827-pcxj-hcmr

## What is CVE-2021-44968?

CVE-2021-44968 is a high-severity use after free vulnerability in n/a, published on 18 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Use after Free vulnerability exists in IOBit Advanced SystemCare 15 pro via requests sent in sequential order using the IOCTL driver codes, which could let a malicious user execute arbitrary code or a Denial of Service (system crash). IOCTL list: iobit_ioctl = [0x8001e01c, 0x8001e020, 0x8001e024, 0x8001e040,0x8001e044, 0x8001e048, 0x8001e04c, 0x8001e000, 0x8001e004, 0x8001e008, 0x8001e00c, 0x8001e010, 0x8001e014, 0x8001e018]

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2021-44968?

It affects 1 product.


Products: Iobit Advanced Systemcare.

## How do I fix CVE-2021-44968?

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

## Is CVE-2021-44968 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-16711](https://insights.sbomify.com/CVE-2018-16711/): Privilege escalation in n/a (high 8.8)
- [CVE-2022-24138](https://insights.sbomify.com/CVE-2022-24138/): Privilege escalation in n/a (high 7.8)
- [CVE-2020-14990](https://insights.sbomify.com/CVE-2020-14990/): Path traversal in n/a (high 7.1)
- [CVE-2020-10234](https://insights.sbomify.com/CVE-2020-10234/): Null dereference in n/a (medium 6.5)
- [CVE-2018-16712](https://insights.sbomify.com/CVE-2018-16712/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44968 and fix it if it is affected.

What it is: CVE-2021-44968 is a high-severity use after free vulnerability in n/a, published on 18 Feb 2022. 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-2021-44968 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-2021-44968/ (Markdown: https://insights.sbomify.com/CVE-2021-44968/index.md)
```

## Sources

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

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