dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-45750

HIGH · 7.3 CVSS v3.1 Published 2024-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 in TheGreenBow Windows Standard VPN Client 6.87.108 (and older), Windows Enterprise VPN Client 6.87.109 (and older), Windows Enterprise VPN Client 7.5.007 (and older), Android VPN Client 6.4.5 (and older) VPN Client Linux 3.4 (and older), VPN Client MacOS 2.4.10 (and older) allows a remote attacker to execute arbitrary code via the IKEv2 Authentication phase, it accepts malformed ECDSA signatures and establishes the tunnel.

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 VPN Client versions across Windows, Android, Linux, and MacOS contain a vulnerability in the IKEv2 authentication phase. The client improperly validates malformed ECDSA signatures during the authentication handshake, allowing a remote attacker to bypass authentication and potentially execute arbitrary code to establish an unauthorized VPN tunnel.

MitigationUpdate TheGreenBow VPN Client to the latest patched versions available from the vendor. Until patched, restrict network access to trusted VPN gateways only and monitor for unauthorized tunnel establishment.

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

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
Low
Integrity
Low
Availability
Low

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

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 TheGreenBow VPN Client installation
    Check for TheGreenBow VPN Client on the system. On Windows, look for the application in Program Files or Program Files (x86) folders, or check the Start menu. On Linux, check /usr/bin or /usr/local/bin for 'thegreenbow' or 'tgbn'. On Mac, check /Applications for TheGreenBow. On Android, check installed applications list.
    Affected if TheGreenBow VPN Client is installed on the system.
  2. Determine installed version
    On Windows, right-click the application shortcut or executable, select Properties, and check the Details tab for version information. On Linux, run 'thegreenbow --version' or 'tgbn --version' if the binary exists. On Mac, right-click the app in Applications and select Get Info. On Android, go to Settings > Apps > TheGreenBow to view version.
    Affected if The installed version matches or falls within an affected version range (compare to vendor release notes for patched versions).
  3. Verify IKEv2 protocol configuration
    Open TheGreenBow VPN Client configuration for your VPN connections. Navigate to the connection settings or tunnel configuration and check the IKE version or protocol setting. Look for 'IKEv2' as the selected protocol.
    Affected if IKEv2 is configured as the VPN protocol for any active or configured connection.
  4. Monitor for unexpected VPN tunnel activity
    Check TheGreenBow VPN Client interface for any active tunnels that were not initiated by an authorized user. Review connection logs if accessible through the client or system logs for VPN connection events. On Windows, check Event Viewer > Windows Logs > System for VPN-related events.
    Affected if Unexpected or unauthorized VPN tunnels appear in the client interface or connection logs.
  5. Inspect network connections for suspicious VPN activity
    Use system network tools to list active network connections. On Windows, run 'netstat -ano' in Command Prompt and look for IKE (UDP ports 500, 4500) or ESP (protocol 50) connections to unknown gateways. On Linux/Mac, use 'netstat -an' or 'ss -an' with similar port inspection.
    Affected if Active connections to VPN gateways exist that were not initiated by an authorized user or that connect to untrusted gateway addresses.

A user is affected if they have TheGreenBow VPN Client installed with IKEv2 configured, as the vulnerability allows authentication bypass during IKEv2 handshake with malformed ECDSA signatures.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update TheGreenBow VPN Client to the latest patched versions available from the vendor. Until patched, restrict network access to trusted VPN gateways only and monitor for unauthorized tunnel establishment.

Have this fixed Scoped from the published advisory
  • Consultation5.0 h
  • Implementation10.0 h
  • Testing8.0 h
  • Review / QA3.0 h
26.0 hours of engineering $4,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45750 — 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-2024-45750 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