dbcve.org
Ssl Vpn ClientApplication · Stormshield

CVE-2022-46782

HIGH · 7.8 CVSS v3.1 Published 2023-08-05
Fix available
A fix is available. Upgrade to 3.2.0 or later.
See remediation →
80/100
Remediation priority · High
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 was discovered in Stormshield SSL VPN Client before 3.2.0. A logged-in user, able to only launch the VPNSSL Client, can use the OpenVPN instance to execute malicious code as administrator on the local machine.

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 · high confidence

Stormshield SSL VPN Client before version 3.2.0 contains a privilege escalation vulnerability where a logged-in user with limited privileges (able to only launch the VPNSSL Client) can exploit the OpenVPN instance to execute malicious code with administrator privileges on the local machine.

MitigationUpgrade Stormshield SSL VPN Client to version 3.2.0 or later to remediate this privilege escalation vulnerability.

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
Ssl Vpn ClientApplication
Affected:< 3.2.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify Stormshield SSL VPN Client installation
    Check for the presence of Stormshield SSL VPN Client on the system. Common locations include C:\Program Files\Stormshield\ or C:\Program Files (x86)\Stormshield\. Look for directories named 'SSL VPN Client' or 'VPNSSL Client'.
    Affected if The Stormshield SSL VPN Client is installed on the system
  2. Identify installed version
    Locate the main executable (typically vpnssl.exe or similar) and check its version properties. On Windows, right-click the executable, select Properties, and view the Details tab. Alternatively, use PowerShell: Get-ChildItem -Path 'C:\Program Files\Stormshield' -Recurse -Filter '*.exe' | Select-Object Name, VersionInfo
    Affected if Unable to determine version information
  3. Compare version against affected range
    Examine the version number found. The affected version range is any version before 3.2.0. Compare your installed version (e.g., 3.1.0, 3.0.5, 2.x.x) against 3.2.0. Any version starting with 3.0.x or lower, or any 2.x.x version, is affected.
    Affected if Installed version is lower than 3.2.0 (for example: 3.1.0, 3.0.1, 2.8.0)
  4. Check for limited privilege user access
    Determine if there are user accounts on the system with limited privileges that have the ability to launch the Stormshield SSL VPN Client. Review local user group memberships and permissions on the SSL VPN Client executable or start menu shortcut.
    Affected if Non-administrator users have permission to launch the VPNSSL Client

The system is affected if Stormshield SSL VPN Client is installed with a version lower than 3.2.0 AND non-administrative users have the ability to launch the VPN client, allowing them to potentially escalate privileges through the OpenVPN instance.

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 3.2.0 or later
Fixed in 3.2.0
Interim mitigation

Upgrade Stormshield SSL VPN Client to version 3.2.0 or later to remediate this privilege escalation vulnerability.

Recommended fix High confidence

Stormshield SSL VPN Client 3.2.0

  1. Download Stormshield SSL VPN Client version 3.2.0 or later from the official Stormshield vendor source
  2. Install the new version following Stormshield's standard installation procedures
  3. Restart the VPN client service if prompted
  4. Verify the installed version is 3.2.0 or higher to confirm the vulnerability is remediated

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

Fix this in Ssl Vpn Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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