B6U009 for Windows for x64 |
SAS Web Report Studio 4.4_M5 |
Issue(s) Addressed: | Introduced: |
61043 | Drilling to detail data in an OLAP-based SAS® Web Report Studio report might result in an MDX error |
B6U001 |
61274 | A cross-site scripting vulnerability has been identified in SAS® Web Report Studio |
B6U001 |
61904 | Improper error handling might occur in SAS® Web Report Studio |
B6U002 |
62060 | SAS® Web Report Studio might display "HTTP Status 500" when opening a report that contains unresolved data items |
B6U003 |
62191 | In SAS® Web Report Studio, the Text object contains a cross-site scripting vulnerability |
B6U004 |
62312 | SAS® Web Report Studio might display "The system was unable to complete your request" when opening the properties of a report |
B6U005 |
62390 | OLAP-based SAS® Web Report Studio reports that include multiple prompted filters might exhibit poor performance |
B6U005 |
62499 | In SAS® Web Report Studio, the section name field contains a cross-site scripting vulnerability |
B6U005 |
62450 | SAS® Web Report Studio might display HTTP 400 when saving a report to a folder with a Japanese name |
B6U006 |
62876 | SAS® Web Report Studio images contain a cross-site scripting vulnerability |
B6U006 |
63115 | Prompted, synchronized SAS® Web Report Studio reports that use an OLAP data source fail to open |
B6U006 |
62370 | OLAP dimensions defined with a period for the All level cannot be resized in SAS® Web Report Studio |
B6U007 |
62972 | SAS® Web Report Studio URL has a cross-site scripting vulnerability |
B6U008 |
64019 | NLNUM format is not honored when accessing a SAS® Web Report Studio report via a remote link or URL |
B6U009 |
NOTE: If you install this hot fix, you must also install hot fix B6W009 for SAS BI Report Services 4.4_M5. |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
B6W009 for Windows for x64 |
SAS BI Report Services 4.4_M5 hot fix for SAS Web Report Studio 4.4_M5 |
Issue(s) Addressed: | Introduced: |
61043 | Drilling to detail data in an OLAP-based SAS® Web Report Studio report might result in an MDX error |
B6W001 |
61274 | A cross-site scripting vulnerability has been identified in SAS® Web Report Studio |
B6W001 |
61904 | Improper error handling might occur in SAS® Web Report Studio |
B6W002 |
62060 | SAS® Web Report Studio might display "HTTP Status 500" when opening a report that contains unresolved data items |
B6W003 |
62191 | In SAS® Web Report Studio, the Text object contains a cross-site scripting vulnerability |
B6W004 |
62312 | SAS® Web Report Studio might display "The system was unable to complete your request" when opening the properties of a report |
B6W005 |
62390 | OLAP-based SAS® Web Report Studio reports that include multiple prompted filters might exhibit poor performance |
B6W005 |
62499 | In SAS® Web Report Studio, the section name field contains a cross-site scripting vulnerability |
B6W005 |
62450 | SAS® Web Report Studio might display HTTP 400 when saving a report to a folder with a Japanese name |
B6W006 |
62876 | SAS® Web Report Studio images contain a cross-site scripting vulnerability |
B6W006 |
63115 | Prompted, synchronized SAS® Web Report Studio reports that use an OLAP data source fail to open |
B6W006 |
62370 | OLAP dimensions defined with a period for the All level cannot be resized in SAS® Web Report Studio |
B6W007 |
62972 | SAS® Web Report Studio URL has a cross-site scripting vulnerability |
B6W008 |
64019 | NLNUM format is not honored when accessing a SAS® Web Report Studio report via a remote link or URL |
B6W009 |
|