XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XSA-468: multiple Windows PV driver vulnerabilities - update now!

    Scheduled Pinned Locked Moved News
    57 Posts 14 Posters 1.6k Views 11 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C Offline
      conitrade-as
      last edited by

      After upgrading the VM tools the mitigation script still shows vulnerable devices on some hosts. After running the script to apply the mitigations, nothing is reported as being vulnerable anymore.

      Thus the question: Is applying the mitigations a necessary action as well? Or does installing the v9.4.1 tools fix the vulnerability?

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        dinhngtu Vates 🪐 XCP-ng Team @conitrade-as
        last edited by dinhngtu

        @conitrade-as Installing the XenServer 9.4.1 tools and rebooting (a couple times) will be enough. Do your VMs show as vulnerable (red) or unable to detect (orange)? There are some new host XAPI updates for correcting driver version reporting that are needed for the XO feature to work.

        C D 3 Replies Last reply Reply Quote 0
        • C Offline
          conitrade-as @dinhngtu
          last edited by

          @dinhngtu Ok, I will keep that in mind as I go through all the VMs. As I currently cannot update XCP-ng on all hosts (8.2.1 LTS), the VMs where the new tools were installed and mitigations applied show up as "orange".

          On a XCP-ng 8.3 test hosts with all updates applied the detection works as advertised.

          1 Reply Last reply Reply Quote 0
          • D Offline
            DustinB @dinhngtu
            last edited by

            @dinhngtu said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

            @conitrade-as Installing the XenServer 9.4.1 tools and rebooting (a couple times) will be enough.

            The multiple reboots is the annoying part, ha... working on my systems now. I've always used https://www.xenserver.com/downloads for this.

            On numerous VM's I've been installing over top of the existing drivers and within System Manager I still see

            75f32119-dd49-4c5d-a906-1f7d33822369-image.png.

            Should I just uninstall the old stuff first, then install the updated to address?

            D 1 Reply Last reply Reply Quote 0
            • D Offline
              dinhngtu Vates 🪐 XCP-ng Team @DustinB
              last edited by

              @conitrade-as The XAPI update was backported to 8.2.1 LTS so you could update your hosts for the new display.

              @DustinB If you're coming from old XenServer tools to new, no need to uninstall.

              D 1 Reply Last reply Reply Quote 0
              • D Offline
                DustinB @dinhngtu
                last edited by

                @dinhngtu said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

                @DustinB If you're coming from old XenServer tools to new, no need to uninstall.

                Interesting, the alert is still within XOA

                9cf6c8e6-5d08-4469-896b-7e0905730607-image.png ...

                D 1 Reply Last reply Reply Quote 0
                • D Offline
                  dinhngtu Vates 🪐 XCP-ng Team @DustinB
                  last edited by

                  @DustinB Do you have the newest pool updates? The warning depends on that.

                  D 1 Reply Last reply Reply Quote 0
                  • D Offline
                    DustinB @dinhngtu
                    last edited by

                    @dinhngtu said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

                    @DustinB Do you have the newest pool updates? The warning depends on that.

                    I have an open ticket for that.....

                    1 Reply Last reply Reply Quote 0
                    • C Offline
                      conitrade-as @dinhngtu
                      last edited by

                      @dinhngtu On a Windows 10 VM rebooting alone did not do the trick. After 5 reboots the script still reports vulnerable devices:

                      .\Install-XSA468Workaround.ps1 -Scan
                      
                      Looking for vulnerable XenIface objects
                      Found vulnerable object XENBUS\VEN_XSC000&DEV_IFACE\_
                      Found vulnerable object XENBUS\VEN_XSC000&DEV_IFACE\_
                      
                      Looking for vulnerable XenIface WMI GUIDs
                      Found vulnerable WMI GUID 1D80EB99-A1D6-4492-B62F-8B4549FF0B5E
                      Found vulnerable WMI GUID 12138A69-97B2-49DD-B9DE-54749AABC789
                      Found vulnerable WMI GUID AB8136BF-8EA7-420D-ADAD-89C83E587925
                      
                      Found XenIface vulnerability, it's recommended to run the script
                      True
                      

                      Running .\Install-XSA468Workaround.ps1 works as expected. After another reboot nothing is reported as being vulnerable anymore.

                      On a Windows 2019 Server I saw the behaviour you described: Installing the tools and a reboot was enough.

                      C D 2 Replies Last reply Reply Quote 0
                      • C Offline
                        conitrade-as @conitrade-as
                        last edited by

                        On another Windows 10 host it worked. What was different: I saw the message box "Tools have been installed successfully". May be that makes a difference?

                        1 Reply Last reply Reply Quote 0
                        • D Offline
                          dinhngtu Vates 🪐 XCP-ng Team @conitrade-as
                          last edited by dinhngtu

                          @conitrade-as I saw that on your Windows 10 VM, the "Manage Citrix PV drivers via Windows Update" option is enabled. That one might have needed a Windows Update to install the fixed drivers. Do you have that option enabled in other VMs?

                          C 1 Reply Last reply Reply Quote 0
                          • C Offline
                            conitrade-as @dinhngtu
                            last edited by

                            @dinhngtu On the machine where it worked, the option "Manage Citrix PV drivers via Windows Update" was not enabled. Seems that my older BIOS Windows 10 VMs have that option enabled. On all UEFI VMs the options is disabled.

                            As I wanted to go and check that is present in the templates, I realized that the Windows Templates are gone from Xen Orchestra v5.106.4???

                            D 1 Reply Last reply Reply Quote 0
                            • D Offline
                              DustinB @conitrade-as
                              last edited by

                              @conitrade-as said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

                              As I wanted to go and check that is present in the templates, I realized that the Windows Templates are gone from Xen Orchestra v5.106.4??

                              Can confirm all templates for Windows are missing on 5.107.0 as well.

                              D M pdoniasP 3 Replies Last reply Reply Quote 0
                              • D Offline
                                dinhngtu Vates 🪐 XCP-ng Team @DustinB
                                last edited by dinhngtu

                                @conitrade-as @DustinB Thanks, reported the template issue to XO team.

                                1 Reply Last reply Reply Quote 0
                                • C Offline
                                  conitrade-as
                                  last edited by conitrade-as

                                  Here is another interesting fact: After installing the new tools (v.9.4.1) my static routes in Windows were all gone. ⚠ Definitively a good way to loose connectivity to your domain controller. And that's why you have good monitoring and store things in Ansible et al. ... 🙂

                                  D C F 3 Replies Last reply Reply Quote 0
                                  • D Offline
                                    DustinB @conitrade-as
                                    last edited by

                                    @conitrade-as said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

                                    Here is another interesting fact: After installing the new tools (v.9.4.1) my static routes in Windows were all gone. ⚠ Definitively a good way to loose connectivity to your domain controller. And that's why you have good monitoring and store things in Ansible et al. ... 🙂

                                    Statically assign, but keep your DHCP server with reservations to address these types of issues 🙂

                                    C 1 Reply Last reply Reply Quote 0
                                    • M Offline
                                      manilx @DustinB
                                      last edited by

                                      @DustinB Did run usr/bin/create-guest-templates but tepmlates are gone here also.

                                      D 1 Reply Last reply Reply Quote 0
                                      • D Offline
                                        DustinB @manilx
                                        last edited by

                                        @manilx said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

                                        @DustinB Did run usr/bin/create-guest-templates but tepmlates are gone here also.

                                        I did not, I'm in the middle of an AV/EDR migration and this way added to the list of things to touch while I was on the systems.

                                        To me the templates are a minor inconvenience as we aren't constantly adding VMs.

                                        1 Reply Last reply Reply Quote 0
                                        • C Offline
                                          conitrade-as @DustinB
                                          last edited by

                                          @DustinB Not IP assignments, I am talking about static routes. See e.g. https://learn.microsoft.com/en-us/powershell/module/nettcpip/get-netroute

                                          D 1 Reply Last reply Reply Quote 0
                                          • D Offline
                                            DustinB @conitrade-as
                                            last edited by

                                            @conitrade-as said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

                                            @DustinB Not IP assignments, I am talking about static routes. See e.g. https://learn.microsoft.com/en-us/powershell/module/nettcpip/get-netroute

                                            Okay.... what...

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post