dbcve.org
Aruba Virtual Intranet AccessApplication · Hp

CVE-2022-23678

MEDIUM · 5.9 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 4.3.0 or later.
See remediation →
68/100
Remediation priority · Elevated
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
A vulnerability in the Aruba Virtual Intranet Access (VIA) client for Microsoft Windows operating system client communications that could allow for an attacker in a privileged network position to intercept sensitive information in Aruba Virtual Intranet Access (VIA) client for Microsoft Windows operating system versions: 4.3.0 build 2208101 and below. Aruba has released upgrades for Virtual Intranet Access (VIA) Client that address this security vulnerability.

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

A vulnerability in the Aruba Virtual Intranet Access (VIA) client for Windows allows an attacker with privileged network position to intercept sensitive information transmitted through the VPN client communications.

MitigationUpgrade Aruba VIA client for Windows to a version newer than 4.3.0 build 2208101.

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
Aruba Virtual Intranet AccessApplication
Affected:< 4.3.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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 Aruba VIA client is installed
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Aruba*VIA*"}' in PowerShell
    Affected if No Aruba VIA entry is found in installed programs
  2. Locate the Aruba VIA executable
    Check for the VIA client executable typically in C:\Program Files\Aruba\VIA\ or C:\Program Files (x86)\Aruba\VIA\, or search for 'ViaClient.exe' using Get-ChildItem
    Affected if The executable is not found in expected locations
  3. Retrieve the installed version number
    Right-click the ViaClient.exe file, select Properties, go to the Details tab, and note the File Version; alternatively, run '(Get-Item "C:\Program Files\Aruba\VIA\ViaClient.exe").VersionInfo.FileVersion' in PowerShell
    Affected if The version shown is blank or cannot be determined
  4. Compare version against the affected range
    Compare the retrieved version number to 4.3.0 - note that the fix version is 4.3.0 build 2208101
    Affected if The installed version is lower than 4.3.0 (for example, 4.2.x, 4.1.x, or any version below 4.3.0)
  5. Confirm the VPN client configuration
    Launch the Aruba VIA client if installed and verify it is configured to connect; the vulnerability affects traffic transmitted through active VPN sessions
    Affected if The client connects to corporate resources and transmits sensitive data over the VPN tunnel

The environment is affected if Aruba VIA client for Windows is installed with a version number lower than 4.3.0 and the client is actively used or configured to transmit sensitive communications.

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

Upgrade Aruba VIA client for Windows to a version newer than 4.3.0 build 2208101.

Recommended fix High confidence

Aruba Virtual Intranet Access (VIA) 4.3.0 or later (build above 2208101)

  1. Navigate to the Aruba Networks support portal and download the latest Aruba Virtual Intranet Access (VIA) client for Windows
  2. Uninstall the current Aruba VIA client from the affected Windows system
  3. Install the new VIA client version 4.3.0 or higher (build greater than 2208101)
  4. Launch the VIA client and verify the installed version in the About or Settings section

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

Fix this in Aruba Virtual Intranet Access Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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