These release notes are for the WhiteSource cloud solution, and do not apply to the on-premises solution that has its own release notes. Click hereto view known issues.
...
| Info |
|---|
IMPORTANTBeginning in version 21.3.2, WhiteSource will be modifying the various topics, plus the overall structure, of the documentation. This includes editing and condensing the existing content (therefore archiving certain topics) for better usability, removing unnecessary and/or duplicate content, and restructuring the topic hierarchy for a logical flow. Since this project will be a “work in progress” for an unspecified amount of time, WhiteSource apologizes in advance for any inconvenience this might cause. |
Version 21.8.1.1 (31-August-2021)
Resolved Issues
Removed unreachable libraries from the Unified Agent’s jar.
Version 21.8.1 (29-August-2021)
...
Jira Server Plugin (Beta)
Resolved an issue that occured occurred when using an Oracle database.
Resolved Issues
In the Unified Agent, the excludes parameter was being called for every project in a folder, instead of per project directory.
In the Unified Agent, when scanning a target folder while extracting a jar file, a null pointer exception occurred.
A Prioritize scan would fail with an EUA error due to missing SHA-1 library dependency.
An Artifactory Plugin scan would fail to get the SHA-1 library dependency.
...
Azure DevOps Integration Version 21.7.21 (17-August-2021)
Resolved Issues
In the Azure DevOps Services Integration, authentication issues required downgrading the azure-devops-node-api NPM library used by the extension.
...
Support was extended to the latest Jira Server versions.
Resolved Issues
In the Library Security Vulnerabilities page, when the same library appeared in several projects, the wrong shield was displayed.
Under certain conditions, when using the Vulnerabilities Report, an error occurred.
In the Unified Agent, when scanning in SCM mode, a debug exception occurred before cloning the repository.
In the Unified Agent, when scanning yarn projects, the hierarchy tree was not deduped, resulting in memory issues.
A runtime error occurred in the Artifactory plugin.
The minutes-to-milliseconds conversion during cloning of WhitesourceService.class caused an invalid value in wss.connectionTimeoutMinutes.
When scanning via Github scanner, when scanning a repository by a tag (not branch), the scan failed in the cloning phase.
...
A new report, the Early Warnings Report, is released. This report displays same-day indications of vulnerabilities automatically identified by WhiteSource even before being certified by the Researchers. The report has limited availability for select customers. It is being slowly rolled out and will be available for all customers and environments in the next couple of weeks, a separate notice will be announced in the release notes for GA.
Note that as was announced on June 6th, on August 15th the Multiple Library Version report will replace the alert for Multiple Library Version, which will be disabled for all customers. All information that was available in Multiple Library Version alerts will be available in the dedicated report, for both past and future scans.
Resolved Issues
When the same NuGet dependency was defined in both the csproj and nuspec, it appeared twice in the application.
In the Unified Agent, setting multiple archives in the "-d" argument sometimes led to incorrect results.
The Maven, OCaml, Modules, and the R resolvers of the Unified Agent were not failing the scan if the relevant package manager was not installed when failErrorLevel was set to ALL.
In the Unified Agent, the parameter gradle.additionalArguments was only being applied to a subset of Gradle commands, instead of all Gradle commands.
When scanning projects with the Unified Agent, and archiveIncludes and archiveExtractionDepth were set, corrupted zip files resulted in null pointer exceptions in certain Java versions.
In the Unified Agent, the Maven resolver did not detect the dependency tree path when the Maven log was altered.
...
New and updated documentation has been published for the Global Org/Organization/Product/Project-Level APIs and Product and Project-Level APIs.
The information in the Utilizing Security Vulnerabilities Information was moved to Understanding and Managing Security Vulnerabilities, and the page was deprecated.
The main API page, HTTP API v1.3, will be deprecated on September 1, 2021. All the information contained in this page already appears in the API sub-topics, such as Product and Project-Level APIs, etc.
...
The library path was added to the Jira ticket.
Resolved Issues
In the Security Alerts reports, there were no checks to determine if the organization had partial data property.
Jira Server Plugin: instead of assigning the WhiteSource issue type only to the relevant project, it was added to all the screens in the user's Jira environment.
...
Azure DevOps Integration Version 21.6.31 (14-July 2021)
Resolved Issues
In the Azure DevOps Services Integration, a corrupted setting of the extension was not handled correctly.
Azure DevOps Integration Version 21.6.3 (8-July 2021)
Resolved Issues
In the Azure DevOps Services Integration, an issue prevented executing the WhiteSource task.
Version 21.6.2.2 (6-July 2021)
Resolved Issues
In the Unified Agent, when the gradle.preferredEnvironment parameter was set to wrapper, gradle commands were executed instead of gradlew commands.
Azure DevOps Integration Version 21.6.2.1 (5-July 2021)
Resolved Issues
In the Azure DevOps Services Integration, an issue prevented updating the project settings.
...
A new variable for specifying options for the Java command executing the Unified Agent's JAR is now available in the Bitbucket integration.
Resolved Issues
The IntelliJ IDE would cease to function when scanning Maven projects with the WhiteSource plugin.
When a server was stopped, there were problems continuing the scan that had already started.
Persist ManagedResource failed after a database Lock exception.
Manually remapping of all the source files did not close pending requests for the old source library.
In the Unified Agent, projectPerFolderIncludes failed to detect subfolders.
When scanning a Yarn project with the Unified Agent, if the "resolved" section was missing for a dependency within the yarn.lock file, a Null Pointer Exception occurred.
WhiteSource now supports the ability to run bower and yarn in the same directory.
In the case of GitHub.com integration, the SCM scanner scanned the root folder instead of the cloning folder, causing the scanner to scan additional libraries.
...
Beginning in this version, support is added for Cargo workspaces.
Resolved Issues
When defined only from the fromDate parameter, the getXXXXAlertsByType API call returned an empty list in VBA mode.
The Vulnerability Report opened with a partial mode disclaimer even in non-partial mode organizations.
In the Unified Agent, NPM 6 failed to resolve dependencies originating from registry.npm.tabao.org.
...
A new report is introduced in beta phase - the Multiple Library Version report. This report displays information regarding multiple versions of the same library that are being used in the selected project/product. With the release of this report, we are announcing that the alert for Multiple Library Version will be disabled to all customers on August 15th, 2021. All information that was available on Multiple Library Version alerts will be available in the dedicated report, for both past and future scans.
Resolved Issues
Under certain conditions in the Library Location Report, the same file locations were displayed multiple times for the same library.
A transitive dependency declared for both the "test" and "compile" scopes was omitted from the scan results.
An NPM scan failed with a null pointer when it identified a package.json missing the name or the version.
In the Unified Agent, a null pointer exception occurred during Maven dependency downloads.
...
When working in Vulnerability-based alerting mode, the Details column was returned to the exported License and Compliance Alerts Report, providing more specific information on the alert.
A new license, Saucy 2.0, has been added. See here for details.
In Vulnerability-based Alerts organizations, new button was added to the pending tasks page, More Information. When selecting tasks from the list (up to 50) and clicking on this button, a new pop-up screen will appear, presenting information regarding the number of vulnerabilities and the license of each of the selected tasks' libraries. The user will be able to change the tasks selection in the pop-up, and the new selection will be saved upon clicking Save. The users will then be returned to the original pending tasks screen, and will be able to choose to approve or reject the tasks, based on the information that was provided in the pop-up
Resolved Issues
In rare cases, there was a discrepancy between the vulnerabilities number shown in the Library page and that shown in the Alerts report.
When the organization's name included the character ".", creating an access key of the issue tracker integration failed.
Queries used to calculate match types fetched all project resource usages of the product/project, taking a long time to return server responses.
The Unified Agent did not handle Gradle artifact relocation correctly.
In some cases, when the Artifactory Plugin deleted Temp folders, not all folders were deleted.
...
The Unified Agent now supports Apache Ivy as part of the Ant dependencies detection.
Resolved Issues
Users encountered errors logging in to WhiteSource.
Project name or project token were mandatory parameters for Docker scanning unnecessarily.
Users were unable to delete roles when there were no roles remaining.
When the Inventory Report was exported to MS Excel, there was extra whitespace between the project name and the Direct Dependency.
When password complexity validation was enabled, users were unable to reset their passwords.
NPM/Yarn downloaded artifacts were not always removed at the end of the Unified Agent scan.
In the Unified Agent, a null pointer exception occurred when scanning ANT-based projects with an empty zip file.
...
Version 21.3.2.2 (19-April-2021)
Resolved Issues
Resolved a security issue in the Jira Server plugin.
Version 21.3.2.1 (13-April-2021)
Resolved Issues
Resolved an issue where running the Unified Agent with “-v” resulted in its version printed with a console log message header.
...
The following documentation changes were implemented:
The Deprecated Features topic was deprecated and the content was moved to the Notices page.
The Setting the Home Page topic was deprecated and the content was moved to the WhiteSource Home Page topic.
The High Severity Bugs Report topic was deprecated.
The File Systemtopic was deprecated.
Structural modifications were implemented to the opening documentation sections, beginning with the login/homepage documentation. As a result, the following pages were deprecated:
Getting Started
Setup Projects
Automate the Process by Using the Unified Agent
In the next version, the R Integration page will be deprecated.
Resolved Issues
Archive extraction of the Zstandard format RPM file failed.
A problem with missing shields occurred during Prioritize scans with NPM due to incorrect handling of duplicate dependencies.
Some Unified Agent's log messages were not taken into account when setting the logLevel parameter.
Running the Generating the Due Diligence Report resulted in a blank report.
When Jira Server was connected to PostgreSQL, an exception occurred in Jira Plugin when trying to add a new row to the table.
...
The Jira Server Plugin is now available in the Atlassian marketplace. Please note that the Jira Server Plugin is currently in beta.
Resolved Issues
Using the Unified Agent’s Archive Extractor when trying to scan the root of the operating system resulted in a null pointer exception.
In AVM, a timeout occurred when fetching vulnerabilities information from Fortify.
...
A new API is now available for unmarking manually-assigned in-house libraries - unmarkManualInHouseLibrary.
Resolved Issues
In some cases, information regarding source libraries was not displayed correctly; for example, empty projects were still displayed in some source libraries, or some source libraries appeared as empty.
Running the gcloud auth command failed during Docker scan on Mac computers.
Users with different roles than admins or alert ignorers were able to ignore alerts in VBA mode.
Exceptions occurred when trying to assign licenses as part of update policy alerts.
In the Unified Agent, when scanning NPM, NPM dependencies were not resolved when package.json did not contain name/version attributes.
When downloading a missing jar file, the Unified Agent incorrectly generated success messages.
Added indication for missing copyright references in the Attribution report summary.
When excluding inner modules (projects) in Gradle, the scan would return the wrong dependencies tree.
Azure DevOps Services Integration: In some cases, adding npm.resolveMainPackageJsonOnly=true to the WhiteSource Configuration task parameter led to a scan failing.
...
Scala dependencies detection was improved, by supporting the sbt-dependency-graph plugin when applicable.
Resolved Issues
When working in vulnerability-based alerting mode, user roles were not being validated when ignoring/reactivating alerts.
New Feature Announcements
WhiteSource is launching a Beta release of a new generic platform for issue tracker integrations and a plugin for Jira Server. The new platform will provide the ability to integrate with issue tracking systems, in order to automatically create issues when a policy match occurs. The Jira Server Plugin is the first integration developed using the new platform and more out-of-the-box plugins are planned to be released.
Documentation
The following topic has been deprecated:
...
Version 21.1.2 (14-February-2021)
Resolved Issues
Azure DevOps Services Integration: Running a pipeline build from a self-hosted agent resulted in a WhiteSource-generated .encrypted file not being deleted at the end of each WhiteSource build task run.
NOTE: Self-hosted agent builds triggered before 14 February may still contain traces of WhiteSource-generated .encrypted files. These files must be manually removed from the self-hosted agent work folder.On rare occasions, library alerts were not created after the vulnerability sync.
Duplicate hashed source files caused the second one to be considered as unmatched.
In Linux, Python scans failed due to a missing space in the execution of one of the commands used for resolution.
In the Unified Agent, there were exceptions when parsing specific pipfile formats.
...
Updated the WhiteSource task version from 20 to 21. In order to use the new version(s) of the extension, you will need to update the task from WhiteSource@20 to WhiteSource@21 inside your pipeline definition.
Added ability to map an Azure Project to an existing WhiteSource Product in addition to creating a new WhiteSource Product) via the Project Settings > Extensions > WhiteSource page.
Resolved Issues
Several issues have been resolved regarding Docker Layers:
Layers with the same SHA1 were represented as one resource.
Layers with a SHA1 already created as “unknown” from previous scans were recognized as that resource, and therefore the display name did not reflect the layer
Layers with SHA1 were unnecessarily looked up in the index
Discrepancies were found between the Alerts Widget and the Library Page.
Vulnerability-based alerting: In the 'Vulnerable Libraries' section on the 'Security Vulnerability' page, the libraries were not filtered by the specific CVE. As a result, the CVEs were ignored and the filter returned all the vulnerable libraries in the organization.
...
The Unified Agent now supports scanning Google Distroless images.
The optimized NPM resolution method, controlled by the npm.resolveLockFile flag, is now the default dependency detection for NPM.
Resolved Issues
Azure DevOps Services Integration: When opening the Security vulnerabilities tab in the Open Source Risk report, the data was not sorted by severity.
Azure DevOps Services Integration: Adding the WhiteSource task to a YAML-based pipeline without setting any of its parameters resulted in an error. As part of this fix, a default value was added for the cwd parameter.
Fixed failures of inventory update if artifactVersion exceeded the valid length.
The Unified Agent failed to parse a non-lowercase configuration value.
The Unified Agent failed to resolve NuGet dependencies when the project.assets.json file was not found in its standard location.
A Python direct dependency, which was also used as a transitive dependency by another library, was not listed as a direct dependency by the Unified Agent.
RPM packages installed or deleted without using yum were not identified correctly by the Unified Agent.
...
A new parameter, python.includePipenvDevDependencies, has been added to provide the ability to manage the dev dependencies. The default value is true.
Resolved Issues
When searching for a library via global search, then searching for a vulnerability via the same search, the page redirects to the library search page.
When resolving several requirments.txt files, the cache of the dependencies was not cleared between the different resolutions.
When running the Unified Agent, the ArchiveExtractor failed to extract files ending with an empty space.
In the “Source File Inventory” report, if users selected to change the library for files they had no permissions to, the Change Library action had no effect and no message was displayed. Now, this action can only be done by selecting the desired files, then Actions > Change Library menu. The users' permissions are validated and a proper message is displayed.
After repeatedly using "Assign Yourself", the pop-up window appears blank and users need to click "Add License Reference" or "Override All” in order to see the mandatory fields.
When running SBT Coursier, the Unified Agent did not run pre-step commands even though pre-step flags were activated.
Changes to licenses being updated either in the index (libraryDataSync API) or in the Admin Console did not trigger alerts calculation.
The Unified Agent did not support the packages.db RPM database
Documentation Updates
The following integration pages have been archived and will therefore no longer be in use. All the material contained therein will be included in the Unified Agent parameter documentation.
...
Version 20.12.1.1 (21-December-2020)
Fixed an issue introduced in the latest version (20.11.2) in which unmatched source libraries were missing from the Project/Product page.
Version 20.12.1 (20-December-2020)
...
Resetting forgotten passwords is now validated with a CAPTCHA test.
A disclaimer has been added to the Library Details page for temporary matches on Go dependencies.
Resolved Issues
For some libraries, the Impact Analysis page did not display results.
Filtering by library in the Attribution Report did not display all results.
In the Web UI, there was no indication when a library contained no licenses. NOTE: Beginning in this version, an indication that review is required is displayed.
In Azure environments, when saving/updating a SAML integration (Domain and Global Account level), an HTTP error 500 was displayed.
In the Vulnerabilities Report, the screen’s legend was unclear.
...
Attribution Report: It is now possible to exclude versions from an exported Attribution Report via API
Resolved Issues
Exceptions occurred when saving Global Account policies.
In the Unified Agent’s scan log, certain Gradle configurations were missing.
Azure DevOps Services Integration: In some cases, build artifacts over 200MB resulted in one of the following errors:
##[error]RangeError: Maximum call stack size exceeded
##[error]Error: "toString()" failed
Azure DevOps Services Integration: In some cases, scanning a project containing an npm project resulted in the following error:
##[error]Error: ENOTDIR: not a directory, scandir '/home/....../node_modules/.bin/acorn'
...
Read-only Permissions: A new auditing role can now be assigned to service users through the setOrganizationAssignments API to give them read-only permissions in the scope of a specific organization.
Resolved Issues
An unexcepted output received from the SBT sbtVersion command caused the Unified Agent to throw an exception.
The Unified Agent didn't handle correctly a possible output of the SBT organization command.
The Unified Agent failed to extract .tar files created with special characters on Linux.
When executing update inventory requests which create a new project, the getProjectVitals/getProductProjectVitals API requests did not display the Unified Agent's version.
When trying to add a new admin from the global admins page, the users list was empty.
When configuring SCM via JSON files, the Unified Agent scanned the current directory.
Project Association: Limitation on the number of items in the products list was removed.
...
A modified Policies page will be launched, with the intent to update existing content, fill in missing gaps, and create a linear flow. This page merges the two existing policies topics - Automated Policies and Managing Policies Throughout Your SDLC. The latter has been archived and is therefore no longer in use.
Resolved Issues
The Unified Agent’s Artifactory scanner failed to build a URL from strings that contained non-alphanumeric characters.
Dependencies defined in the gemfile.lock file with an exclamation mark suffix were wrongly resolved.
Policies where Action was defined as Issue failed to create Work Items issues.
Under certain conditions, when working with policies of the Issue type, exceptions occurred while loading Work Items data.
Resolved Issues - Azure DevOps Services Integration (added 10-November-2020)
Fixed an issue where in some cases, users with non-admin permissions were not able to view the WhiteSource open-source risk report. All existing WhiteSource for Azure DevOps Services extension users will need to approve the extension permission changes that were applied in this version. To approve the new changes, do as follows:
Go to Organization Settings > Extensions > Installed > WhiteSource for Azure DevOps Services.
Click Review. The Authorize WhiteSource for Azure DevOps Services popup is displayed.
Click Authorize.
Scanning a project based on a GitHub Repository led to a RangeError error.
Version 20.10.1.1 (4-November-2020)
...
Azure DevOps Services Integration
Added the ability to specify custom Unified Agent Configuration parameters to be used by a particular pipeline build. For this, a new field, WhiteSource Configuration, was added to the WhiteSource task. For more information, see here.
Documentation Updates
Unified Agent
...
Beginning in version 20.10.2 (approximate release - November 8), a modified Policies page will be launched, with the intent to update existing content, fill in missing gaps, and create a linear flow. This page merges the two existing policies topics - Automated Policies and Managing Policies Throughout Your SDLC. The latter will be archived and therefore no longer be in use.
Resolved Issues
When the project information object did not have a version in its coordinates, the Unified Agent failed to run.
The Unified Agent failed when trying to resolve a large PHP project.
Azure DevOps Services Integration: A pipeline build with the WhiteSource task failed to scan GitHub repositories when using a Linux build agent.
The optimized NPM resolution method, controlled by the npm.resolveLockFile parameter, did not handle duplicate dependencies correctly. This caused an increase in the size of requests sent by the Unified Agent.
When applying Create Issue policies, issues were created incorrectly for all projects in the organization (added November 1, 2020).
When updating group assignments, SAML incorrectly removed users from the domain (added November 1, 2020).
When entering multiple values for either groupAssignments or userAssignments in the setProductAssignments and setOrganizationAssignments API calls, these values were ignored. The fix - from now on, the first value is assigned (added November 1, 2020).
Users were unable to change a source file library if there was already an existing mapping with a comment (added November 1, 2020).
...
The license name of Oracle Development License (as it previously appeared in the application) will now appear according to its official name, Oracle Technology Network License Agreement.
Resolved Issues
During Kubernetes agent scanning, when the scanned component included the same image multiple times, irregularities occurred causing an exception.
In the Attribution report, GPL 2.0 with exception licenses was mistakenly displayed as insert GPL v2 license text here.
When scanning PHP, the Unified Agent threw an exception if one (or more) of the packages did not have a "source" element in the lock file.
...
Beginning in this version, the strict requirement of running the Unified Agent with the configuration file has been removed. If the mandatory parameters are passed to the Unified Agent, in any of the supported methods, the Unified Agent can be run without failing even if the configuration file is missing.
Beginning in this version, if the Yarn lock file (yarn.lock) is found during the scan, it will be used for the dependencies detection, without the need to explicitly set the npm.yarnProject flag.
Resolved Issues
When applying policies to existing inventory from the organizational policies page, the product and project policies were ignored.
When reassigning all of a user’s pending tasks of a user, the inventory request approver was not properly updated.
When two Maven projects were defined with the same name, both projects were created however with partial data. The introduced fix will now add a suffix (_1, _2) to a project name in case there is more than one project with the same name.
...
Helm version 3 support is officially introduced for the Kubernetes integration.
Resolved Issues
If hex.ignoreSourceFiles was set to true, the Unified Agent did not ignore .erl source files.
When groups were created via SAML integration and were then deleted manually from the dashboard, an exception occurred.
...
Fixed CVE-2020-2213
Prioritize
Aggregate Modules mode supported (using the -aggregateModules field).
Functionality Changes
In the Project Association page, the Product column was changed from a selection column to a text column. The project association is now only available by checking the desired project(s) and choosing “Assign to Product”, then choosing the desired product from the drop-down list.
When using “APPEND” update requests, in the rare case where only a TRANSITIVE dependency has been added - the new transitive dependency will be added as a direct dependency, so all of the application's mechanisms such as alerts and policies will be applied on it. This is a change to the current behavior. In order to have the new dependency added as transitive, users can then run another “OVERRIDE” Update Request after the append request.
Resolved Issues
When running the Gradle resolver, if the dependency is missing the Unified Agent will try to download .jar dependencies only.
In the rare use case of a change in the GAV coordinates of an artifact, Gradle scans didn't produce the correct signature for this artifact.
The Request Resolution Status Report displayed the wrong path on the top of the report.
In the Vulnerability Report, the Locations column was missing from the JSON format.
When scanning the plan.json file in a Haskell project, a nullPointerException would occur when building hierarchies where one child did not have dependencies.
In the application’s home screen, some bulk actions of approval/rejection of pending tasks were timed out. This caused the UI to hang and requests were not marked as reviewed.
When scanning a Docker image with source libraries, the “hierarchy” tree included duplications of the source library matched with those source files.
Layer information was missing when detecting FOSS components in Docker .tar files.
...
When a scan for a project is requested while there is already a scan for the same project being executed simultaneously, the new scan is being skipped. Starting in this version, the JSON file returned for the scan will specify the status SKIPPED instead of FINISHED.
Resolved Issues
In cases of empty status files in Debian Docker images, the scan resulted in zero dependencies.
In the Policies screens, a popup indicating that changes will not be saved was displayed even though all changes were properly saved.
A TimeoutException was thrown when calling the method updateNodesParentAndMr in the DependencyNodeRepositoryImpl class.
Priority and Assignee fields appeared in Jira-based policy creation, even when those fields were not defined in the Jira project itself.
Following a change in Jfrog Artifactory version 7 whereby the property name haAwareEtcDir was changed to etcDir, exceptions were thrown in the WhiteSource artifactory plugin.
...
Improvements were made to the Docker scanning of the Linux RPM-based images.
Users can now configure Unified Agent parameters using environment variables.
The Bazel support for Go projects was extended to Windows. The Unified Agent can now scan on both Linux and Windows Go projects using the go_repository rules generated by Bazel Gazelle (see here).
Resolved Issues
When organizations were deleted, data was removed, specifically alerts. This caused timeout exceptions if the table was locked.
Under certain scenarios, a null pointer exception occurred when loading the product assignment.
Under certain conditions, there were problems with dependency resolving from yarn.lock
Under certain conditions in Unified Agent Docker scans, exceptions occurred when there were similar file names but different content or formats.
Kubernetes deployment procedure didn't take into consideration initial configured delays.
When running the Prioritize Multi-Module Analyzer for Gradle, modules that did not have build.gradle were not handled correctly.
Under certain conditions, there were issues with the format of the link field within the policyRejectionSummary file.
Under certain conditions, the Project Associations page loaded slowly and resulted in a 404 error.
...
The "Resolution Request Status" report can now be accessed through the Reports menu.
Resolved Issues
Under certain conditions, the Unified Agent returns no dependencies after failing to parse the packages database when scanning docker images.
In the Source Files widget, after refreshing the page the Change Library column was not displayed.
Under certain conditions, there were inaccuracies in the Effective Usage Analysis Summary Report.
Under certain conditions, the Unified Agent had an issue following a redirect when trying to download a Gradle dependency.
...
Upgraded the following:
WildFly to version 10.1.0
JQuery to version 3.5.0
The Unified Agent’s version is now displayed in the Web Application’s Project Vitals.
The docker image retrieval mechanism was improved resulting in a reduction of the UA scanning time.
Resolved Issues
In the Risk Report, in the General Overview panel, when selecting a product, an incorrect title and link were displayed.
While handling getOrganizationInHouseLibraries requests, a Null Pointer Exception occurred.
In situations where Requires review is the least common license in organization/product/project, the License dashboard ceases to function.
The Attribution Report had issues with a misplaced header.
There were issues with proxy settings in the HTML dependency resolution.
The TeamCity plugin always failed as a result of a check policy request.
Under certain conditions, scanning SBT dependencies resulted with errors.
Local libraries used by a Python project were not detected. This ability was introduced in this release, controlled by the python.localPackagePathsToInstall flag.
...
Version 20.6.1.1 (30-June-2020)
Resolved Issues
Under certain circumstances, the NuGet dependency detection of csproj files resulted in an inaccurate version of the dependency.
...
This version introduces a Dockerized Unified Agent. More information can be found here.
Bazel resolution is now enabled by default. The UA now supports Bazel for Java projects. The following two rules are supported: maven_install, maven_jar.
This version introduces support for OpenSUSE leap images via the Unified Agent Docker scan.
Resolved Issues
Artifactory Docker Virtual Repository scans failed when containing a remote repository.
Under certain conditions, the UA will exit without appropriate log messages.
Under certain circumstances, there was an issue with C# package identification.
In the Library Details page, Only library with effective vulnerability was not displayed.
When trying to create a Jira issue when defining a policy based on vulnerability effectiveness, an exception occurred.
In the Web Application, in the Alerts Report, the EUA “shields” were not displayed.
Jira server issues were not created due to wrong assignee parameters.
During NuGet scans, exceptions were caused following references to missing files.
...
For customers where Prioritize is installed: An “effectiveVulnerabilitiesOnly” flag was added to VULNERABILITY_SEVERITY in Policies API.
Resolved Issues
Under certain circumstances, a specific format of package version in the nuspec file caused a failure in NuGet resolution.
Under certain circumstances, a wrong command was run in NuGet resolution when packages.config is present.
There was no option to provide a full path in a csproj file when referencing other csproj files.
Jira API parameter "query" (which replaced “username”) did not work for all customers.
In the wss_resourceVulnerabilities table, security alerts aren't calculated when there' was no sourceFileHashes mapping.
Under certain circumstances, Ruby scans failed.
In the Unified Agent, when dependencies in Yarn scans had two versions, the scans failed.
...
Beginning this release, the Nuget resolution will be improved and aligned to the other resolvers by excluding the system packages from the scan results by default.
Beginning in this version, the .coffee source files will not be taken into consideration when npm.ignoreSourceFiles is set.
Resolved Issues
Missing proxy support in one of the HTTP calls of the lambda serverless implementation.
Under certain circumstances in Gradle resolution, a hash was calculated on an empty file.
License links that didn’t contain a protocol were considered relative resources in the site, therefore the base URL were added to the href.
After executing actions in the Inventory Report, the selection wasn’t cleared.
When trying to sync a source library which has a duplicate in the database, it tried to remove the existing source library.
Some reports with multiple selection (such as checkboxes) didn’t have any actions to execute on selected items.
When an assignee existed but didn’t appear in the Unified Agent’s initial list, users were unable to create an issue type policy.
Under certain conditions, the Artifactory Plugin would send product parameters as Repository Name in check policy compliance requests.
...
Currently, when entering an invalid role in the setProductAssignments API call, the response is "Successfully set product assignments". Beginning in this version, the response is changed to include the assignments that were successfully set by the API call. Also included is an additional list named “warningMessages” (available from API version 1.3 and up), that includes various warning messages.
In the next Unified Agent release, the NuGet resolution will be improved and aligned to the other resolvers by excluding the system packages from the scan results by default.
Resolved Issues
The License Compatibility report did not recognize licenses that were manually overridden.
Uninstalled OS packages were included in the scan.
Under certain circumstances, the Alert ignorers role was missing from the setProductAssignments API.
The security severity calculations of the "policyStatistics" and "vulnerabilityStatistics" sections of the scan report are not aligned.
Issue with scanned projects including circular symbolic links in Linux.
Unnecessary information printed to the Unified Agent’s log when Azure registry images are scanned
...
This version introduces support for Bamboo server versions up to 7.0.3.
Functionality Changes
Beginning in this version, ignoreSourceFiles is taken into account in the top folder for all cases.
Beginning in this version, Maven resolver will not ignore .jar,.war,.ear,.zip files when ignoreSourceFiles is set.
When setting a Reporter for issues that require one, the reporter will now be chosen from a list (same as selecting an assignee) instead of the previous way where there were text boxes for inserting a Reporter name and display name.
The Unified Agent setting maven.ignoredScopes=NONE is no longer a pre-condition for running Prioritize on Maven projects, but remains as the default setting. Regardless of the Unified Agent configuration file parameter setting, Prioritize analysis will ignore test scope dependencies.
Resolved Issues
Under certain conditions, when the MultiModuleAnalyzer ran on large Gradle multiModule projects, it ignored certain modules.
In Prioritize, the Maven pre-conditions incorrectly used mavenIgnoredScopes.
Under certain conditions, the Unified Agent sent empty dependencies values in offline requests.
Jira projects were not taken into consideration when fetching the mandatory fields to open a Jira issue.
Under certain conditions, some docker image packages (centos) had the same hash value key.
In cases involving the R manager packager, when the match library flag is ON and there is no sha1 for the package, the additional sha1 of this package was ignored.
When fetching the last RVI sync attempt, an OptimisticLockException (AbstractSyncServiceImpl:78) is thrown because another process is updating the same object; hence the version is changed.
When an RVI sync task was created for the first time, it was created without a task name.
Under certain conditions, RedHat libraries were missing from customer databases.
Under certain conditions, after the Docker image (Centos:8) rpm scan ran, there were over 110 items remaining to resolve.
In Jira, under certain conditions, the following occurred due to Jira API changes:
Issues were created without an assignee
When a reporter was defined as mandatory, issues were not created
Adding issue policies via the API failed
This fix applies automatically for new policies. For existing policies, if customers defined a reporter or assignee, they must edit those policies and re-enter the assignee and reporter, and then save.
...
In the Attribution Report, the license text is no longer displayed in the Copyrights section.
In the Plugin Request History report, "fs-agent" has been changed to "unified-agent".
Resolved Issues
A permissions issue existed where the Source File Inventory Report did not filter projects according to user privileges, i.e. users who weren't members of project A were still able to view source files and libraries of that project.
The All Products drop-down list was not sorted alphabetically.
Under certain conditions on large-scale NPM projects, running two scans led to a StackOverflowError.
Under certain conditions, there were parsing irregularities in the modules.txt file.
Under certain conditions, when parsing a “paket.lock” file, an exception occurred.
Under certain conditions, Paket scan results displayed information regarding NuGet.
Under certain conditions, in the Unified Agent, Gradle failed due to the merging of impactAnalysis with failErrorLevel.
In AVM’s Fortify Client, there was an error parsing clients with URLs that contained “ssc”.
Under certain conditions, the maven.ignoredScopes flag did not work as expected.
Maven scans resulted in missing Maven dependencies.
The License Compatibility Report displayed multiple licenses even after using the override function.
The ignoreSourceFiles affected the "includes/excludes" scan results
The default paket.exe path was mistakenly assigned a wrong path.
Under certain conditions, the NuGet resolver contained the wrong version.
...
Previously, in the Library Location Report, when a library had no path it was displayed in the UI as "N/A". This has been changed to an empty string.
Within the next two sprints, WhiteSource will be improving the Unified Agent scan results, mostly regarding Maven resolution. Binaries such as .jar,.war,.ear,.zip will be included in the scan when ignoreSourceFiles is set.
In addition, ignoreSourceFiles will be taken into account in the top folder when packaging appears in the pom file.
Resolved Issues
In some nupkg libraries, libraries which didn’t have a dash ('-') in the display name as the version separator, were not recognized as the same library and therefore did not generate the Multiple Library Versions.
When generated to a .PDF, the Use of Different Versions of Same Library section in the Risk Report had a different title.
Under certain situations, goGradle scans failed with a null pointer exception.
An overlap in the resolvers' bom files resulted in the order of the resolvers being changed.
The Effective Usage Analysis dashboard displayed 0% coverage although vulnerabilities existed.
Under certain conditions, a NoSuchElementException occurred when getting a product approver during update requests.
Under certain conditions, the parsing functionality in Go 1.14 did not work correctly.
Under certain conditions, scans of Docker images resulted in exceptions.
Under certain conditions, new version alerts weren't created.
...
A new API request "getProjectLicensesTextZip" enables project-level scope for the getLicensesTextZip API, providing more granular results for legal business needs.
A new API request "getProjectCopyrightsTextFile" enables project-level scope for the getCopyrightsTextFile API, providing more granular results for legal business needs.
Resolved Issues
When the Multi-Module Analyzer scanned at least a dozen projects, it sometimes randomly failed on some of them; although when scanning a single project, no such problem existed.
...
The Library Details page has been redesigned whereby the information is now organized into four separate tabs.
The Unified Agent now supports SBT 1.3.x and above.
Resolved Issues
In Prioritize, in the Vulnerability Analysis pane, the Analysis Coverage exceeded 100%.
The Unified Agent failed to resolve python dependencies using the virtualenv command.
There were incorrect descriptions for some of the Python libraries.
The Debian importer was unable to download files without release dates.
Under certain situations, CVEs still appeared in the web application even after blacklisting all vulnerable source files.
In Effective Usage Analysis, when the multi-module-analyzer scanned several projects, it sometimes randomly failed some of them, although when it scanned a single project no problem occurred.
"Base directory" was different between the old Unified Agent to the new, thereby causing wrong results to customers.
...
For customers who want to have sources files with associated vulnerabilities identified in WhiteSource when possible, a new optional parameter for getProjectAlertsByType API enables the response to include vulnerable source files.
Resolved Issues
In Prioritize, the Analysis Coverage exceeded 100% in the Effective Vulnerability widget.
Under certain conditions, Scala project scans failed on SBT dependancies.
Under certain conditions, in the Unified Agent, when the 'gradle' commands failed, the Unified Agent did not execute 'gradlew' commands.
Under certain conditions, library folders appeared in the wrong module.
In the Attribution report, the provided license reference was not necessarily the license text itself.
Under certain conditions, after a customer removed an organization, it remained in the customer’s system.
Alerts for new NPM versions included pre-release versions.
...
This version introduces support for the DNF Package manager for CentOS.
Resolved Issues
[Fixed] Under certain conditions, problems occurred when logging in to to the WhiteSource application via Microsoft Azure.
...
A License column has been added to the Attribution Report, enabling users to filter libraries by license in the preview screen.
Added report flexibility: The Attribution Report now enables users to select multiple projects for inclusion in the report’s output.
Resolved Issues
[Fixed] New alerts emails were sent to customers that disabled email notifications.
[Fixed] Under certain circumstances, the License Compatibility Report did not display results.
...
Attribution Report data improvement - When there is no license reference in the library, a generic license will be presented.
Resolved Issues
Under certain conditions, library names were truncated and thus displayed incorrectly in the interface.
...
Attribution Report data improvement - In various cases, a valid license text will be displayed in the report instead of the previously-used JSON/XML.
Resolved Issues
Under certain conditions, library names were truncated and thus displayed incorrectly in the interface.
...
A new screen option, Nested Licenses, provides added granularity for complex cases where nested licenses are being used in a library's repository, such as 3rd party licenses.
In the Due Diligence report, the range of years for the library's copyright (in from-to format) is now displayed in the Copyright column. Additionally, in the By Copyrights filter, it is now possible to filter according to the from-to values.
Resolved Issues
[Fixed] Under certain conditions, newly-imported JavaScript libraries were included in Gitta lookups.
[Fixed] After closing a request for a Source Library, a new request was opened again after scanning.
[Fixed] Under certain conditions, Null Pointer Exceptions occurred when the CVSS 3 extraData field was null.
[Fixed] When passing float values to the client, these values changed their original value, causing incorrect data to be presented.
[Fixed] Due to the system path of the Gradle dependencies, the EUA analysis coverage was inaccurate.
[Fixed] When inserting a copyright date range in the Due Diligence report, the report did not filter properly and the results were therefore inaccurate.
[Fixed] When the Unified Agent .jar file was extracted while running, the Unified Agent would cease to function.
...
Beginning in this version, WhiteSource Developer Integrations will have its own release notes. Please refer here.
Resolved Issues
[Fixed] Under certain conditions in app.whitesourcesoftware.com, some libraries were missing although the update request contained them.
[Fixed] Servers received imported licenses that have license names but no license types, resulting in no license creation.
[Fixed] Under certain conditions, the Unified Agent did not collect all the dependencies in yarn projects.
[Fixed] Under certain conditions, it was impossible to create sub-task issues using Jira integration.
[Fixed] When trying to create a new copyright template without years, an error was displayed.
[Fixed] When exporting HTML attribution report by project in partial data organization, an error was displayed.
[Fixed] Under certain conditions, the Unified Agent Docker Hub scan returned no results.
[Fixed] An out-of-memory issue occurred for Yarn.
[Fixed] Detect configurations did not work correctly for GO projects.
Release Unified Agent version 19.11.1
...
The Unified Agent now runs Effective Usage Analysis even if npm.includeDevDependencies is set to false.
Resolved Issues
[Fixed] After creating an issue, when trying to parse the JSON response from Jira, an exception occurred, resulting in Jira issues created several times for the same libraries in the same projects.
[Fixed] In the Attribution Report, XML was not displayed properly (for example, XML tags were removed).
[Fixed] In specific circumstances, the Gradle resolver did not create a full dependency tree, resulting in missing libraries from Docker image scans.
[Fixed] When trying to upload an offline request with a specific Gradle dependency, the dependency was not found in the inventory.
[Fixed] Uploading a metadata file to the WhiteSource application resulted in errors.
[Fixed] In WhiteSource for Bitbucket Server, WhiteSource for GitHub Enterprise, and WhiteSource for GitHub.com, when an issue for multiple components was created, the Automatic Remediation information was displayed.
Release Unified Agent version 19.10.1
...
The GPL 2.0, MPL 1.0, MPL 1.1, and MPL 2.0 licenses now have a copyright risk score of 65.
Risk analysis information was added for the GPL 1.0 and OpenSSL licenses.
Resolved Issues
[Fixed] An error in the RVI sync process caused the alert creation to fail.
[Fixed] A null pointer exception occurred while calculating the check policy hash.
[Fixed] In the Risk Report, when a project had duplicate dependencies in the hierarchy, negative values were displayed.
[Fixed] WhiteSource for GitHub Enterprise, WhiteSource for GitHub.com - Duplicate GitHub Issues were generated for the same library and CVE when multiple scans were triggered in parallel for a commit.
Release Unified Agent version 19.9.2
...
An indicator has been added to WhiteSource for GitHub Enterprise, WhiteSource for GitHub.com and WhiteSource for BitBucket Server indicating when automatic remediation is available for the specific vulnerability.
WhiteSource is launching the WhiteSource for GitLab Core beta version, enabling GitLab users to access WhiteSource security alerts within GitLab’s native environment.
Resolved Issues
[Fixed] The getChangesReport API request was disregarding the time specified in the "startDateTime" field, fetching results from 00:00 on the specified date.
[Fixed] In an EUA-enabled organization, under certain conditions in 'Library Security Vulnerabilities' view, projects referencing the vulnerability were not filtered by the projects to which the user has privileges, resulting in errors.
[Fixed] In some cases, the Containers dashboard did not display any results.
[Fixed] WhiteSource for GitHub Enterprise - When upgrading to image version 19.8.1, a Java error in the wss-ghe-app logs is displayed.
...
Release Unified Agent version 19.9.1
Release WhiteSource Advise for Chrome 19.9.1
Version 19.8.1 (8-September-2019)
...
The API requests getProductLicenses, getOrganizationLicenses, and getProjectLicenses have an optional new field, excludeProjectOccurrences (default value = false) which enables getting product/domain licenses without project occurrences.
Resolved Issues
[Fixed] In the Risk Report PDF, in the Policy Name field, Chinese characters were omitted.
[Fixed] In selected instances when Prioritize’s multi-module setup failed, the log reported it as successful.
[Fixed] The response of the "getAllOrganizations" API request yields a "Success" message in scenarios where it should fail.
[Fixed] When resolving Yarn dependencies, the wrong line was printed in the log.
[Fixed] The Unified Agent did not identify all SBT dependencies in the *compile.xml file.
...
WhiteSource Advise for Chrome now detects licensing and vulnerabilities information on Rust packages found in Rust-related websites.
WhiteSource Advise for Chrome now detects licensing and vulnerabilities information on Haskell packages found in Haskell-related websites.
WhiteSource Advise for Chrome now detects licensing and vulnerabilities information on OCaml packages found in OCaml-related websites.
Resolved Issues
[Fixed] If SAML has been configured, under certain conditions login failed with a NullPointerException.
[Fixed] On a Go project using the Godep dependency manager, the Unified Agent did not find all GO dependencies.
...
The new Configuration Recommendation mode identifies the environment that the user wants to scan and creates the configuration file automatically.
Added flexibility in Gradle projects scanning: New configuration parameter 'gradle.includedScopes' enables defining which scopes will be included in the scan.
This version provides support for Serverless Framework via a dedicated plugin.
Resolved Issues
[Fixed] Users were unable to create a policy with an 'Issue' action linking to their 'Work Items' tracker type.
[Fixed] Under certain conditions, after a project was updated, a server failure message was displayed.
[Fixed] In the Security section in the Risk Report, large numbers did not display correctly.
[Fixed] When a request was assigned to a group, conditions did not appear in Pending Tasks.
[Fixed] Under certain conditions, the Unified Agent failed to retrieve projects from Artifactory.Releases.
...
For customers using Application Vulnerability Management platforms such as ThreadFix or Fortify, this version introduces the synchronization of Open Source Software scanning results from WhiteSource to the aforementioned platforms.
Resolved Issues
[Fixed] In the Users page, the names do not sort correctly in alphabetical order.
[Fixed] In the Risk Report, in the Security area, when displaying data with a large number of libraries, the last digit was displayed in a line of its own.
[Fixed] Users received errors when trying to approve their library requests.
[Fixed] The Library Details page was stuck indefinitely with a “Loading Data” message.
[Fixed] When trying to approve tasks from the Pending Tasks screen, users received a message stating insufficient permissions.
[Fixed] Using the Unified Agent on Windows 10 via command line led to “illegal operations” warnings.
[Fixed] When configuring ‘excludeDependenciesFromNodes’, the wrong dependency was excluded.
[Fixed] File paths with special characters caused the Unified Agent to crash.
[Fixed] When activating WhiteSource Advise, using the wrong regular expression in the URL caused the activation process to fail.
...
A new CLI parameter, detect, automatically creates a configuration file based on your scanned libraries and files (relevant for all package managers). NOTE: This is the first step in new configuration recommendations. Future versions will contain additional features.
Added flexibility by supporting custom build environments: The Unified Agent now has the ability to pass arguments to the gradlew and gradle ‘dependencies’ command. A new configuration parameter was added for this purpose, gradle.additionalArguments.
This version adds support for scanning Go 1.11 projects without the need for a dependency manager.
Resolved Issues
[Fixed] Projects were limited to exporting 32766 lines.
[Fixed] In the Users page, when the page was reduced, the column names were hidden.
[Fixed] When generating a Risk Report with a large number of libraries, the last digit was displayed in its own line.
[Fixed] Under certain conditions, failures occurred when trying to resolve Python dependencies.
[Fixed] The Unified Agent took an excessively long time to run.
[Fixed] When trying to approve requests and clicking Override and Approve, administrators were sent back to the Home page with a message notifying insufficient permissions.
[Fixed] When an API request for the getProjectAlertsReport was sent, the output was an .xlsx file in which the last title, Library Type, and the entries underneath it were not in the same column.
...
New streamlined multi-module process - In the multi-module Prioritize, a new command-line parameter, overrideExistingSetup = true, enables users to remove the pause between multi-module steps.
Resolved Issues
[Fixed] In the Inventory report, when match by filename was not selected, a filename match still occurred.
[Fixed] Under certain conditions, alerts weren't removed for deleted vulnerabilities.
[Fixed] Handling changed paths and vulnerability traces tasks took over 10 hours to complete.
[Fixed] After performing the Apply to Pending Requests action on product-level policies, a “server error” message was displayed.
[Fixed] Several identical licenses were assigned to the same library.
[Fixed] The API call getProductRiskReport took an excessively long time to run.
[Fixed] In the Dashboard, in License Analysis, clicking Facebook BSD + Patents displayed an empty report even though the relevant license exists.
[Fixed] When retrieving Gitta cached results under certain conditions, a NullPointerException was displayed.
[Fixed] When handling update requests, an exception occurred.
[Fixed] The Unified Agent experienced memory issues.
[Fixed] When scanning a GitLab repository using Source Control Management (SCM) configuration, an error message was received.
[Fixed] WhiteSource Bolt for Azure report was not available in the Azure DevOps multi-stage pipelines preview.
[Fixed] When integrating Prioritize with Gradle, the log analysis process failed for sub-modules.
[Fixed] Under certain conditions, the config file mistakenly created a new WhiteSource directory instead of including all configuration settings in the build directory.
[Fixed] R resolvers-library name is not according to DESCRIPTION dependency file package.
[Fixed] Docker scans would hang when retrieving images.
[Fixed] In the Unified Agent, in the log, different parameters had the same name.
[Fixed] The Library WhiteList did not block Reject policy violations.
[Fixed] After the Unified Agent scanned .js files, some of the files were replaced by other versions with a different SHA-1 version.
[Fixed] Under certain conditions, the WhiteSource Application did not identify NuGet packages.
[Fixed] Under certain conditions, when the Unified Agent ran on NuGet, it did not clear the packages directory and failed on a second run.
[Fixed] The Unified Agent log displayed thousands of attempts to access irrelevant URLs.
[Fixed] A proper error message for the Python errors in the debug log level was not generated.
[Fixed] Python dependencies were not resolved in hierarchical mode.
...
Extended JFrog Artifactory Integration -
Support updating JFrog Artifactory “properties” tab of an artifact with vulnerabilities and licensing information from WhiteSource scan.
Support accessing JFrog Artifactory repository using a token for enhanced security. The following configuration parameters were added: ‘artifactory.accessToken’, ‘artifactory.url’.
Support more informative summary statistics at the end of a scan - displaying different language extensions for which binary/source files were found and for each extension how many source/binary files were scanned.
Resolved Issues
[Fixed] In certain scenarios in alerts report when using a filter on the report the screen was hanging with “Loading Data” message.
[Fixed] JIRA integration - An error was returned while trying to create a JIRA ticket as part of a policy action due to missing JIRA credentials set.[Fixed] In certain scenarios request processing time of the application was very long in Azure EU system.
[Fixed] In certain scenarios when manually changing the origin library of two different libraries consecutively the "Show me some options" results of the second library are refreshed only after few seconds.
[Fixed] HTML resolver - In certain scenarios an error occurred when resolving HTML dependencies.
[Fixed] In some cases when scanning Android projects there were created duplicated entries in the inventory.
[Fixed] WhiteSource Bolt activation for Azure DevOps Server 2019 failed due to registration phase error.
[Fixed] In certain scenarios archive extraction didn’t work correctly for some jar & war files.
[Fixed] WhiteSource For Containers - Docker image which was configured in the ‘docker.includes’ parameter wasn’t scanned.
[Fixed] When running a scan using UA with debug mode the reported path in the log was the executable path instead of file path.
[Fixed] When running UA with command line parameters which include “.” in their names using PowerShell a parsing error was returned.
[Fixed] In certain scenarios when a proxy is configured in the UA configuration file an error was returned from a scan.
...
Maven Plugin: Support creating empty projects in WhiteSource for maven projects with multi-modules when some of the modules are empty by using a new configuration parameter ‘updateEmptyProject’.
Resolved Issues
[Fixed] In certain scenarios when the request with source files to match is very large (over 1M source files) there was an error from Gitta lookup.
[Fixed] In certain scenarios there were several issues with libraries incorrectly identified with security vulnerabilities or ignore comments were deleted.
[Fixed] Attribution Report - extra separation lines added when adding Header text.
[Fixed] Informative text on Alert Ignorers is missing in the Admin → Assignments page in Product level.
[Fixed] In certain scenarios when applying in house rules on pending requests the process took a long time. Performance improvement was done.
[Fixed] UA fails to resolve Ant dependencies due to external Ant parameters. New configuration parameter was added: ‘ant.external.parameters’ which should contain comma separated list of <key=value> pairs.
...
GitHub integration: Added the ability to enable/disable the creation of open issues after the scan has been completed.
Resolved Issues
[Fixed] In certain scenarios the number of libraries displayed on the ‘Top 10 Products’ panel may be different than the number of libraries displayed on the specific product page.
[Fixed] Ignored Alerts report: Comments are not displayed after the project is filtered.
[Fixed] Unified Agent: In certain scenarios when the configuration parameter ‘npm.includeDevDependencies’ is set to ‘true’, the scan ignores this setting.
[Fixed] Unified Agent Go code with Gogradle environment: Issue may occur when passing information to the Unified Agent while using a custom build file ('build-inner.gradle') and settings file ('settings-inner.gradle')
[Fixed] Informative text on Alert Ignorers is missing in the Admin → Assignments page.
...
Release management automation: Added the ability to obtain an attribution report via the API requests ‘getProductAttributionReport’ and ‘getProjectAttributionReport’.
The ‘getProjectComparisonReport’ API provides a project comparison report in an Excel format.
Resolved Issues
[Fixed] Alerts report may not always be updated after the source files are moved to a new source library.
[Fixed] Classification of specific Microsoft ASP.NET libraries may be erroneous.
[Fixed] Library Details page: Library type column of Alerts table is not always populated.
[Fixed] Requests may occasionally pause when a JIRA issue is created during a request update.
[Fixed] When the 'go.dependencyManager' parameter is not defined, the Unified Agent may not go through all the supported resolvers.
...
Enhanced resolution for Maven projects that include multiple libraries with the same SHA-1. In these cases, the library page displays a new hyperlink stating "This SHA-1 has multiple matches: Click here to override the original match". Clicking the hyperlink will open a pop-up window, enabling a user to manually select alternative GAV coordinates from a list.
Optimized accuracy of data in Security Trends Dashboard:
After clicking on a chart, the related Alerts report only displays security vulnerability alerts.
The dashboard keeps its predefined context after navigating to another GUI page.
...
Note: The ability as a 'Product Default Approver' or 'Product Administrator' to assign licenses/copyrights has been removed.
Resolved Issues
[Fixed] In specific settings the ‘getVulnerabilitiesBetweenDates’ API call may not function properly.
[Fixed] Attribution report: In certain browsers, the 'Library' column may not be properly displayed.
[Fixed] 'Set as Home Page' option does not work with SAML.
[Fixed] Project Page: The Library pane size may change when switching between ‘Flat list’ and ‘Hierarchy’ views.
[Fixed] Attribution report: Occasionally, issues may occur while exporting the report as a ‘.txt’ file.
[Fixed] Gradle based projects: Issues may occur during the scan in specific cases when no source files are in the project.
...
Enhanced service user automation: The new API call 'createServiceUser' enables adding a service user.
The following API calls enable fetching a list of all custom attributes along with their set of values for each library on a Project/Product/Organization level: ‘getOrganizationCustomAttributeValues’, ‘getProductCustomAttributeValues’, ‘getProjectCustomAttributeValues’.
Improved automation for granular policy enforcement: Added API calls to manage policies on a Project level. These API calls include ‘getProjectPolicies’, ‘addProjectPolicy’, ‘updateProjectPolicy’, ‘removeProjectPolicies’, ‘reorderProjectPolicyPriorities’.
Resolved Issues
[Fixed] Library Version Comparison page: An error in loading the page may occur for specific libraries.
[Fixed] In specific libraries, the alert on a library is marked as ‘ignored’, but the scan still fails.
[Fixed] Inventory report: Sorting by license may not always display the report in the desired order.
Unified Agent:
[Fixed] An error related to the stopwatch class has been fixed.
[Fixed] In certain cases, the temporary WhiteSource directory names may be too long and their paths may exceed 260 characters.
...
The ‘productName’ parameter is now supported in the CLI when running the xModuleAnalyzer. See also related documentation.
Resolved Issues
[Fixed] Ignored Alerts report: Manual comments may not be displayed properly.
[Fixed] Attribution report: Issues may occur when exporting a report with the ‘Reference generic license’ option selected.
[Fixed] Security Trends Dashboard: The entire organizational data is displayed for all users, including the users who do not have permissions to view all of the Products.
[Fixed] Effective Usage Analysis (EUA): A Java exception may occur when running the Unified Agent with both Gradle and Maven related parameters enabled.
...
The new Containers vulnerabilities report displays the vulnerabilities per pod, namespace, and cluster. It enables the user to filter specific resources according to their context in the cluster. See also related documentation
Attribution report: Missing copyright references are now marked with an asterisk (‘*’) character.
It is possible to export the following reports in JSON format via the GUI or via an API request: Alerts report, and Vulnerabilities report.
Due Diligence report: Added option to view the report data only for a specific project, in addition to a particular product.
Resolved Issues
[Fixed] Unified Agent: Microsoft TFS Integration: An ‘Invalid diff JSON structure’ error may be displayed in specific configuration settings.
[Fixed] An error message is not displayed when trying to create a user via the 'Create User' functionality, and providing an email address of a user that already exists with the same email address.
Inventory report:
[Fixed] The ‘Primary Attribute’ is not included in the export output of the report.
[Fixed] A number of options in the search dropdown menu are not displayed when searching by product name.
[Fixed] In certain scenarios the ‘Suspected unspecified license’ filter erroneously displays no records in the results.
[Fixed] Risk report: PDF output may include issues when exporting the report for a selected product.
[Fixed] Occasional pauses may occur while submitting new libraries via the Drag and Drop UI.
[Fixed] ‘Admin’ → ‘Users’ page → ‘Invite Users’ button: Email addresses that include a space as the last character of the address are not processed, and an error message is displayed.
[Fixed] The process of renaming a project may occasionally require a relatively long interval, and no indication is displayed on when the process will be completed.
[Fixed] SAML: Single Sign On (SSO) may not work properly after a certificate update.
[Fixed] In specific configurations a source library may be uploaded without its source files after the scan.
[Fixed] Security Trends Dashboard: Issues may occur in the output when selecting 3 months and 6 months time frames.
[Fixed] In certain configurations libraries may be matched by their name although the ‘Match libraries by filename’ checkbox is cleared.
...
It is possible to export the following reports in JSON format via the GUI or via an API request: Inventory report, Source File Inventory report, and Due Diligence report. The following API requests include a new optional parameter called 'format'. The format is 'xlsx' by default, and valid options include 'json' and 'xlsx': ‘getOrganizationInventoryReport’, ‘getProductInventoryReport’, ‘‘getProjectInventoryReport’, ‘getOrganizationSourceFileInventoryReport’, ‘getProductSourceFileInventoryReport’, ‘getProjectSourceFileInventoryReport’, ‘getOrganizationDueDiligenceReport’, ‘getProductDueDiligenceReport’.
Risk Report: Added an ‘Apply’ button for the selected scope (Organizational or Product) that generates the report only after it is pressed.
Attribution Report: A new option enables the user to select one of the following outputs in cases where the license reference cannot be obtained:
Leave license blank
Reference a generic license
Resolved Issues
Jira Integration:
[Fixed] Unclear error message is displayed when the Issue Tracker URL is invalid.
[Fixed] In certain scenarios, exceptions may occur when fetching Jira mandatory fields.
[Fixed] Manual Comments: The ‘&’ and ‘%’ characters are classified as illegal characters, and therefore, some URLs cannot be entered.
[Fixed] The Attribution report does not fully support foreign language characters in Unicode.
[Fixed] The ’getOrganizationProjectVitals’ API request may require a relatively long time to complete.
Unified Agent:
[Fixed] When scanning a remote repository (using SCM settings), the Unified Agent also scans the directory where the Unified Agent was executed.
[Fixed] In certain Yarn based projects, dev dependencies are resolved even though the parameter ‘npm.includeDevDependencies’ is set to ‘false’.
[Fixed] The ‘productToken’ parameter is always ignored when running the Unified Agent with the ‘-requestFiles’ CLI parameter.
[Fixed] A returned output message is out of context when the Unified Agent runs on an SBT project without a defined target folder.
...
Checks API support for GitHub Integration: Added support for the Completed with 'Neutral' conclusion. See also related documentation. This conclusion is displayed when a 'push' command is not valid. See also related documentation.
Attribution Report: Added custom attributes specified for the component in the summary report for both HTML and Text export formats.
Risk report: Added the ‘How Do We Compare?’ section to the PDF export of this report.
License compatibility report: Added an option to export the report in Excel and XML formats.
Unified Agent:
The following updates were made as part of the overall plan to move to a single scanning interface:
JAR file changed to ‘wss-unified-agent-<x.x.x>.jar’
Configuration file changed to ‘wss-unified-agent-<x.x.x>.config’
License changed from Open Source (Apache) to a WhiteSource Commercial license.
New distribution repo on GitHub (unified-agent-distribution)
Backwards compatible (fs-agent-distribution and fs-agent repositories are still available for previous open source versions of the Unified Agent)
The checkbox ‘Add project to default product when only project name is provided’ has been added to the ‘Integrate’ tab.
If only 'projectName' is provided in the configuration file (‘projectToken’, ‘productName’, ‘productToken’ are left empty), and the checkbox is not selected (default), then the first found project with the identical name is overridden. If the checkbox is selected in the same scenario, then the project is added by default to the product named 'My Product'.Added the configuration parameter 'failErrorLevel', which sets additional scenarios to 'error' instead of 'success'.
Resolved Issues
Unified Agent:
[Fixed] Issues may occur while scanning a multi-module SBT project.
[Fixed] Issues may occur while scanning multiple projects on Bamboo.
Effective Usage Analysis (EUA):
[Fixed] While using the multi-module feature, sub modules are being overridden due to identical names. See also related documentation on updates to the setup file.
[Fixed] The summary of the Effective and non Effective libraries may not always match when comparing them on a Product vs. Project level.
[Fixed] High Severity Bugs report: An error may occur in the generation of the report in specific scenarios.
[Fixed] Attribution report: HTML export of report does not support Chinese characters.
API:
[Fixed] It is not possible to create a product with a name that includes non-Latin characters.
[Fixed] A fetched Due Diligence report in Excel format may not be properly formatted.
...