# CVE-2023-27470: Race condition in n/a

> A local attacker can exploit a race condition in the update service to delete arbitrary files via a pseudo-symlink.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-2vhw-q36q-j3v5

## What is CVE-2023-27470?

CVE-2023-27470 is a high-severity vulnerability in n/a, published on 11 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BASupSrvcUpdater.exe in N-able Take Control Agent through 7.0.41.1141 before 7.0.43 has a TOCTOU Race Condition via a pseudo-symlink at %PROGRAMDATA%\GetSupportService_N-Central\PushUpdates, leading to arbitrary file deletion.

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

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

It affects 1 product.


Products: N-Able Take Control.

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

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

## Is CVE-2023-27470 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27470 exists.

Public exploit code:

- https://github.com/3lp4tr0n/CVE-2023-27470_Exercise (github_poc): https://github.com/3lp4tr0n/CVE-2023-27470_Exercise

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27470 is a high-severity vulnerability in n/a, published on 11 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27470 exists.

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-2023-27470/ (Markdown: https://insights.sbomify.com/CVE-2023-27470/index.md)
```

## Sources

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

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