dbcve.org
Thegreenbow Vpn ClientApplication · Thegreenbow

CVE-2023-47267

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-19
Fix available
A fix is available. Upgrade to 6.52.006 / 6.87.108 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

TheGreenBow Windows VPN Client (versions 6.52, 6.87) contains a privilege escalation vulnerability where attackers can manipulate memory mapped files to gain elevated (administrator) privileges on the affected Windows systems. This is a local privilege escalation flaw with critical severity (CVSS 9.8).

MitigationApply the vendor-supplied security patch for TheGreenBow VPN Client. If no patch is available, consider restricting interactive use of the VPN client, implementing application whitelisting, and ensuring endpoint detection is active.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Thegreenbow Vpn ClientApplication
Affected:>= 6.52.004, < 6.52.006>= 6.87.001, < 6.87.108>= 6.87.001, < 6.87.109

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if TheGreenBow VPN Client is installed
    Open Windows Settings > Apps > Apps & features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed software. Look for entries containing 'Thegreenbow' or 'VPN Client'.
    Affected if The software is present on the system
  2. Retrieve the installed version number
    In Programs and Features, click on TheGreenBow VPN Client and view the Version column. Alternatively, check the file properties of the main executable (typically in Program Files or Program Files (x86) under a Thegreenbow folder).
    Affected if The displayed version falls within these affected ranges: 6.52.004 through 6.52.005, 6.87.001 through 6.87.107, or 6.87.001 through 6.87.108 (note: version format may display as 6.52.004 or similar)
  3. Check if VPN client services are running
    Open Services (services.msc) and look for TheGreenBow services, or run 'Get-Process | Where-Object {$_.ProcessName -like "*tgb*" -or $_.ProcessName -like "*greenbow*"}' in PowerShell.
    Affected if TheGreenBow processes or services are actively running on the system (required for the privilege escalation to be exploitable)

You are affected if TheGreenBow VPN Client is installed with a version matching 6.52.004-6.52.005, 6.87.001-6.87.107, or 6.87.001-6.87.108, and the client is installed or has been run on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.52.006 / 6.87.108 / 6.87.109 or later
Fixed in 6.52.0066.87.1086.87.109
Interim mitigation

Apply the vendor-supplied security patch for TheGreenBow VPN Client. If no patch is available, consider restricting interactive use of the VPN client, implementing application whitelisting, and ensuring endpoint detection is active.

Recommended fix High confidence

TheGreenBow VPN Client 6.52.006 (for 6.52.x line) or 6.87.109 (for 6.87.x line)

  1. 1. Ensure all active VPN connections are closed and the TheGreenBow VPN Client is not running
  2. 2. Navigate to the official TheGreenBow website (www.thegreenbow.com) to download the updated VPN Client
  3. 3. Download version 6.52.006 if using the 6.52.x product line, or version 6.87.109 if using the 6.87.x product line
  4. 4. Run the installer with appropriate administrative privileges
  5. 5. Follow the installation wizard prompts to complete the upgrade
  6. 6. After installation, verify the client version matches the expected fixed release
  7. 7. Test VPN connectivity to ensure the upgrade did not disrupt existing configurations
Caveat Standard security update; verify VPN configuration compatibility after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Thegreenbow Vpn Client Scoped from the published advisory
  • Consultation6.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,032.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47267 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47267 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data