CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2019-5544 remediation guide

VMware VMware ESXi and Horizon DaaS

OpenSLP as used in ESXi and the Horizon DaaS appliances has a heap overwrite issue. VMware has evaluated the severity of this issue to be in the Critical severity range with a maximum CVSSv3 base score of 9.8.

Open CVE record
ProductVMware VMware ESXi and Horizon DaaS
Affected versionsESXi 6.7 prior to patch release ESXi670-201912001, ESXi 6.5 prior to patch release ESXi650-201912001, ESXi 6.0 prior to patch release ESXi600-201912001 and Horizon DaaS 8.x prior to BZ-2467224-Disable_SLPD_service_permanently_801_Hotfix., >= 8.0.0 < 9.0.0.0, 6.0, 6.5, 6.7, 7.0, 6.0 s390x, 7.0 s390x, 7.7 s390x, 6.0 ppc64, 7.0 ppc64, 7.7 ppc64, 7.0 ppc64le, 7.7 ppc64le, 7.7, <= 2.0.0, 30, 31
Fixed versions9.0.0.0
Priority basisImmediate · CVSS 9.8 · EPSS 96.8%
01

Identify the affected asset

Confirm whether VMware VMware ESXi and Horizon DaaS is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: ESXi 6.7 prior to patch release ESXi670-201912001, ESXi 6.5 prior to patch release ESXi650-201912001, ESXi 6.0 prior to patch release ESXi600-201912001 and Horizon DaaS 8.x prior to BZ-2467224-Disable_SLPD_service_permanently_801_Hotfix., >= 8.0.0 < 9.0.0.0, 6.0, 6.5, 6.7, 7.0, 6.0 s390x, 7.0 s390x, 7.7 s390x, 6.0 ppc64, 7.0 ppc64, 7.7 ppc64, 7.0 ppc64le, 7.7 ppc64le, 7.7, <= 2.0.0, 30, 31. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2019-5544 Remediation Guide | SECUFOCUS NOW