* * * READ ME * * *
                 * * * Veritas Risk Advisor 7.1.1 * * *
                         * * * Hot Fix 3 * * *
                         Patch Date: 2016-10-07


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Risk Advisor 7.1.1 Hot Fix 3


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Windows 64-bit



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.1.1_HF3
* 3901544 (3901542) *Veritas Risk Advisor 7.1.1 HF3


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:

Patch ID: 7.1.1_HF3

* 3901544 (Tracking ID: 3901542)

SYMPTOM:
*Cross Site Scripting Vulnerability
*Brocade Network Advisor (BNA) scan timeout failure issue
*Can't connect to virtual server through proxy (WMI) 
*Unable to scan vCenter 
*HDLM Paths not collected in certain cases on Windows  False Ticket reported
*Ticket export to PDF
*Sudo misconfiguration errors
*Sudo misconfiguration errors
*Exception in Oracle ASM Disk Group collection
*Exception in DB File To OS Object collection
*Exception in Host Configuration Differences Risk Signature
*Incorrect data collection from HDS machines
*Comparison module worksheet exception 
*Business Entities issue

DESCRIPTION:
*As part of an internal security audit to the AvailabilityGuard we added security
enhancements to the product that close the XSS vulnerabilities [N-311]
*Added parallel scanning methods to the collector of the BNA management console
[N-290]
*The Jar files were updated to a newer version that support NTLM v2 [N-201]
*The Jar files were updated to support a newer version of the API [N-326]
*The HDLM command returned paths but did not list the drive letter for the dynamic
volume.
As a result there was incorrect number of paths in the risk signature [N-174]
*Fixed formatting issues with tickets that are exported to PDF [N-214]
*Bug fixed [N-246]
*Bug fixed [N-318]
*Bug fixed [N-319]
*Bug fixed [N-320]
*Bug fixed [N-321]
*Bug fixed [N-321]
*Bug fixed [N-256]
*Bug fixed [N-289]

RESOLUTION:
*Veritas has modified the code to resolve these issues.



INSTALLING THE PATCH
--------------------
1.    Download the patch VRA_7.1.1.3.exe and copy it to the master VRA server.
2.    On the master VRA server, stop the VRA web server using the following steps:    
    Open a command line window running with administrator privileges
    Enter the following commands: 
# net stop TomcatWatchDog
# net stop tomcat8
3.    Locate the VRA folder. By default, it is in the path: 
C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\ 
4.    Make a copy of the VRA folder and store it in another location (do not store the copy under the tomcat tree). The patch updates files in this folder, so if you need to revert to the unpatched version of VRA, you will need the original folder.
5.    Go to the folder where you downloaded the patch. Find VRA_7.1.1.3.exe and double-click it.
6.    Follow the steps in the wizard to install the patch. 
7.    On the master VRA server, start the VRA web server using the following steps:
    Open a command line window running with administrator privileges
    Enter the following commands: 
# net start tomcat8
# net start TomcatWatchDog
8.    Login to VRA. 
9.    Verify that the build number is correct. On the VRA main screen, click "About". The build number should be 40148.


REMOVING THE PATCH
------------------
Veritas strongly recommends that you install the patch. However, if after installing it you need to revert to the unpatched version of VRA 7.1, use the following procedure:

1.    Make sure you still have the backed up copy of the pre-patched, version 7.1 VRA folder
2.    On the master VRA server, stop the VRA web server using the following steps:
    Open a command line window running with administrator privileges
    Enter the following commands: 
# net stop TomcatWatchDog
# net stop tomcat8
1.    Locate the VRA folder. By default,  it is in the path:
C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\ 
2.    Delete the "VRA folder"
3.    Copy the backed up folder to its original location.  If you have changed the name of the copied folder, make sure to rename it to "VRA" (not including the quotes).
10.    On the master VRA server, start the VRA web server using the following steps:
    Open a command line window running with administrator privileges
    Enter the following commands: 
# net start tomcat8
# net start TomcatWatchDog


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE