dbcve.org
Horizon ClientApplication · VMware

CVE-2023-34037

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
VMware Horizon Server contains a HTTP request smuggling vulnerability. A malicious actor with network access may be able to perform HTTP smuggle requests.

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

VMware Horizon Server contains an HTTP request smuggling vulnerability that allows a network-adjacent attacker to manipulate how HTTP requests are parsed between front-end and back-end components. This desync attack can enable bypass of security controls, cache poisoning, or session hijacking by smuggling malicious requests through the server.

MitigationApply the VMware security patch for this vulnerability when released, or implement network segmentation and WAF rules to filter abnormal HTTP request patterns.

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
Horizon ClientApplication
Affected:= 2006= 2012= 2103= 2106= 2111= 2111.1= 2203= 2212

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Locate VMware Horizon Client installation
    Check for VMware Horizon Client installation on Windows systems by examining the installation directory (commonly Program Files\VMware\VMware Horizon Client\) or querying the Windows Registry under HKLM\SOFTWARE\VMware, Inc.\VMware Horizon Client
    Affected if VMware Horizon Client is installed on the system
  2. Determine installed version number
    Retrieve the version of the VMware Horizon Client by accessing the executable properties (horizonclient.exe) in the installation folder, or run: wmic product where "name like 'VMware Horizon Client'" get version,Name,InstallDate
    Affected if The installed version matches any of the following: 2006, 2012, 2103, 2106, 2111, 2111.1, 2203, or 2212
  3. Assess network exposure
    Determine if the VMware Horizon Client is used in environments where it processes HTTP requests from network sources, such as when connecting through a VMware Horizon Gateway or in scenarios where untrusted HTTP traffic could reach the client components
    Affected if The client is configured to accept remote HTTP connections or is accessible across network boundaries without proper request filtering

The environment is affected if VMware Horizon Client version is exactly 2006, 2012, 2103, 2106, 2111, 2111.1, 2203, or 2212, and the client processes HTTP requests from network-adjacent sources.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the VMware security patch for this vulnerability when released, or implement network segmentation and WAF rules to filter abnormal HTTP request patterns.

Recommended fix High confidence

VMware Horizon Client 2203 or later (latest stable release recommended)

  1. 1. Verify the current installed version of VMware Horizon Client by checking 'Add or Remove Programs' or the application's 'About' section
  2. 2. Download the latest version of VMware Horizon Client from the official VMware website (www.vmware.com) or your VMware subscription portal
  3. 3. Uninstall the current version of Horizon Client from all affected systems
  4. 4. Install the latest Horizon Client version (2203 or later recommended) on each affected workstation
  5. 5. After installation, verify the version by checking Help > About in the client
  6. 6. Test that the client can connect to Horizon servers successfully
Caveat Ensure compatibility with your Horizon Server version - verify that your server supports the new client version before upgrading

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

Fix this in Horizon Client Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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