# CVE-2023-47267: Privilege escalation in n/a

> Attackers can gain escalated privileges by crafting changes to a memory mapped file in TheGreenBow Windows VPN Client.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jp88-vhh7-qm8q

## What is CVE-2023-47267?

CVE-2023-47267 is a critical vulnerability in n/a, published on 19 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue discovered in TheGreenBow Windows Enterprise Certified VPN Client 6.52, Windows Standard VPN Client 6.87, and Windows Enterprise VPN Client 6.87 allows attackers to gain escalated privileges via crafted changes to memory mapped file.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Thegreenbow Thegreenbow Vpn Client.

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

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

## Is CVE-2023-47267 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2918](https://insights.sbomify.com/CVE-2009-2918/): Null dereference in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47267 is a critical vulnerability in n/a, published on 19 Dec 2023. 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-2023-47267 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-2023-47267/ (Markdown: https://insights.sbomify.com/CVE-2023-47267/index.md)
```

## Sources

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

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