# CVE-2019-20000: Race condition in n/a

> A time-of-check time-of-use race condition in BullGuard's malware scan allows attackers to delete privileged files via symbolic links.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9238-pwgr-pmp5

## What is CVE-2019-20000?

CVE-2019-20000 is a medium-severity vulnerability in n/a, published on 26 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The malware scan function in BullGuard Premium Protection 20.0.371.8 has a TOCTOU issue that enables a symbolic link attack, allowing privileged files to be deleted.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 1 product.


Products: Bullguard Premium Protection.

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

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

## Is CVE-2019-20000 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20000 is a medium-severity vulnerability in n/a, published on 26 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-20000 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-20000/ (Markdown: https://insights.sbomify.com/CVE-2019-20000/index.md)
```

## Sources

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

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