Fixed Issues

The following customer-reported issues have been fixed in this release:

  • (HUB-47462). Fixed an issue where a user who was previously set as a project owner or who originally created the project did not appear in the assignable project owner dropdown in Project Settings > Project Details.

  • (HUB-47780). Fixed an issue where users assigned the Project Manager role who also possessed the Global Project Creator role were erroneously permitted to assign arbitrary project roles when adding users to a project.

  • (HUB-47795, HUB-48744). Fixed an issue where updating vulnerability remediation via the LTS Remediation API (PUT /api/lts-projects/.../remediation) failed to persist the remediationStatus for CVE-primary vulnerability entries that had linked BDSAs.

  • (HUB-47891). Fixed an inconsistency on the Project BOM page where vulnerability entries prioritized BDSA over CVE even when the system security ranking was configured to prioritize NVD over BDSA.

  • (HUB-48058). Fixed an issue where exporting a BOM to SPDX (versions 2.3 and 3.0) did not format specific component usage types (such as Implementation of a Standard and Dev. Tool / Excluded) correctly, causing them to revert to default values upon re-import.

  • (HUB-48059). Fixed an issue where the /api/projects/{projectId}/versions/{projectVersionId}/review-components endpoint ignored limit and offset pagination parameters when queried with the bomMatchReviewType:unmatched filter.

  • (HUB-48223). Fixed an issue where the Updated timestamp for projects displayed on the Dashboard was not refreshed after project setting modifications, rescans, or BOM updates.

  • (HUB-48225). Fixed an issue in Match Review where attempting to confirm a component match that contained multiple origins failed with an HTTP 412 error.

  • (HUB-48228). Fixed an issue where changing the version or origin of a manually identified component on the BOM tab resulted in an HTTP 404 error and caused the component to be unintentionally deleted after refreshing the page.

  • (HUB-48232). Fixed an issue where navigating to the Source tab on certain project versions resulted in an undefined project ID error in the API request URL, preventing source BOM entries from loading.

  • (HUB-48248). Fixed an issue in the reporting database where scan_stats_view populated empty user_id values for code locations containing archived scan entries.

  • (HUB-48250). Fixed an issue where snippets marked as ignored unexpectedly reappeared in exported SBOM reports.

  • (HUB-48260). Fixed an edge case on the BOM page where distinct components sharing identical names were omitted from the component list when pagination limits were applied.

  • (HUB-48371). Fixed an issue where vulnerabilities from deeply nested subprojects were not rolled up transitively or displayed at the top-level parent project view.

  • (HUB-48416). Fixed an issue where multiple instances of the on-demand KbUpdateWorkflowJob-Component Version Security Update job were queued and executed concurrently while previous instances were still in progress, causing excessive JobRunner resource utilization.

  • (HUB-48465). Fixed an issue where vulnerability remediation updates and status changes were not recorded in the project version activity journal.

  • (HUB-48466). Fixed an issue where searching for components in use (/api/search/components-in-use) using quoted strings did not prioritize exact matches at the top of the search results.

  • (HUB-48515). Fixed an issue where the Affected Projects list incorrectly displayed container layer components that had been removed or replaced.

  • (HUB-48586). Fixed an issue where Black Duck SCA scans intermittently failed during BOM preparation with an unexpected NOT_INCLUDED scan status.

  • (HUB-48614). Fixed an issue where uploading CycloneDX SBOM files containing certain Package URLs (such as Go pseudo-versions or special characters) failed with error ERR05_1022 Unable to process SBOM matching request.

  • (HUB-48617). Fixed an issue where exported CycloneDX SBOM reports contained mismatched vulnerability scores and identifiers compared to what was displayed on the UI BOM.

  • (HUB-48689). Fixed a regression where querying the /vulnerable-bom-components endpoint with filter=ignored:true failed to return components marked with component-level ignores.

  • (HUB-48696). Fixed an issue where Black Duck Detect scans utilizing the detect.project.user.groups parameter failed if the scanning user lacked global administrative permissions.

  • (HUB-48709). Fixed an issue where searching projects via /api/projects?q=name:<project> returned duplicate project records when a user held access through both direct assignment and project group memberships.

  • (HUB-48752). Fixed an issue where policy rules evaluating the condition Unconfirmed Snippets equals Yes were erroneously triggered by ignored snippet matches.

  • (HUB-48767). Fixed an issue where exported CycloneDX 1.6 and SPDX 3.0 SBOM reports omitted associated BDSA entries and populated unassociated CVE records instead.

  • (HUB-48842). Fixed an issue where binary scans intermittently failed with ERR05_1079 Internal Server Error due to a transient 403 response during SCASS status polling.

  • (HUB-48857). Fixed an issue where generated SBOM reports included vulnerability entries referencing components and versions that were not part of the project's BOM.

  • (HUB-48896). Fixed a UI regression in Snippet View where candidate match details in the Alternative Matches dropdown were misaligned and truncated.

  • (HUB-49090). Fixed an issue where users assigned direct access to a project could not be designated as the project owner.