Lucene search

K
symantecSymantec Security ResponseSMNTC-111181
HistoryDec 11, 2019 - 12:00 a.m.

Xen CVE-2019-19577 Denial of Service Vulnerability

2019-12-1100:00:00
Symantec Security Response
www.symantec.com
10

Description

Xen is prone to a denial-of-service vulnerability. Attackers can exploit this issue to crash the affected application, denying service to legitimate users. Xen Xen version through 4.12.0 are vulnerable.

Technologies Affected

  • Citrix Hypervisor 8.0
  • Citrix XenServer 7.0
  • Citrix XenServer 7.1 LTSR CU2
  • Citrix XenServer 7.6
  • Xen Xen 2.0
  • Xen Xen 3.0.2
  • Xen Xen 3.0.3
  • Xen Xen 3.0.4
  • Xen Xen 3.1
  • Xen Xen 3.1.3
  • Xen Xen 3.1.4
  • Xen Xen 3.2
  • Xen Xen 3.2.0
  • Xen Xen 3.2.1
  • Xen Xen 3.2.2
  • Xen Xen 3.2.3
  • Xen Xen 3.3
  • Xen Xen 3.3.0
  • Xen Xen 3.3.1
  • Xen Xen 3.3.2
  • Xen Xen 3.4
  • Xen Xen 3.4.0
  • Xen Xen 3.4.1
  • Xen Xen 3.4.2
  • Xen Xen 3.4.3
  • Xen Xen 3.4.4
  • Xen Xen 4.0
  • Xen Xen 4.0.0
  • Xen Xen 4.0.1
  • Xen Xen 4.0.2
  • Xen Xen 4.0.3
  • Xen Xen 4.0.4
  • Xen Xen 4.1
  • Xen Xen 4.1.0
  • Xen Xen 4.1.1
  • Xen Xen 4.1.2
  • Xen Xen 4.1.3
  • Xen Xen 4.1.4
  • Xen Xen 4.1.5
  • Xen Xen 4.1.6.1
  • Xen Xen 4.10
  • Xen Xen 4.10.0
  • Xen Xen 4.10.1
  • Xen Xen 4.10.2
  • Xen Xen 4.11.0
  • Xen Xen 4.12.0
  • Xen Xen 4.2
  • Xen Xen 4.2.0
  • Xen Xen 4.2.1
  • Xen Xen 4.2.2
  • Xen Xen 4.2.3
  • Xen Xen 4.3
  • Xen Xen 4.3.0
  • Xen Xen 4.3.0-1
  • Xen Xen 4.3.1
  • Xen Xen 4.4
  • Xen Xen 4.4.0 -
  • Xen Xen 4.4.0
  • Xen Xen 4.4.1
  • Xen Xen 4.5
  • Xen Xen 4.5.0
  • Xen Xen 4.5.3
  • Xen Xen 4.6.0
  • Xen Xen 4.6.3
  • Xen Xen 4.7.0
  • Xen Xen 4.8
  • Xen Xen 4.8.0
  • Xen Xen 4.8.4
  • Xen Xen 4.9
  • Xen Xen 4.9.0
  • Xen Xen 4.9.1
  • Xen Xen 4.9.2
  • Xen Xen 4.9.3

Recommendations

Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
Ensure that only trusted users have local, interactive access to affected computers.

Block external access at the network boundary, unless external parties require service.
If global access isn’t needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.

Updates are available. Please see the references or vendor advisory for more information.

References