3.8September 2024 | Note |
|---|
Upgrade Migration Notifications |
Please note: As of ThreadFix 3.8, OpenShift is no longer supported ThreadFix Kubernetes version supports 1.27 The ThreadFix CLI tool will be deprecated in a future release The defect description text format for Azure DevOps Defect tracker in the Classic_Description.vm file has been updated
Key UpdatesThe character limits for email, username, and First/Last have been increased to 25 characters The list of currently accepted file types for uploading to findings has been updated to include the following: .csv .fpr .json .nessus .ozasmt .xml csv doc docx JPEG JPG PDF PNG xls xlsx
Improvements to error messaging Minor UI improvements
Addressed Reported Issues Addressed issue where a manually closed vulnerability may display as having been reopened by a scan upload Addressed issue with importing .fpr file types Addressed issue where Time to Remediate policies for new teams/applications may not display correctly in the UI Addressed an issue where Snyk may not allow a new scan to be imported if there is prior data present
To view a complete list of changes and updates, including prior releases, please view the 3.X Version Feature Changes list. 3.7April 2024 | Note |
|---|
Upgrade Migration Notifications Users must be on version 3.6 to upgrade to 3.7. Users interested in migrating to 3.7 from 2.X must upgrade to 2.8.9.1first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Kafka changes. For REST API updates, refer to the Change Log.
|
Helm Addressed Reported Issues Resolved issue of not being able to set a Parent field during a Jira ticket creation Resolved an issue where users may receive an error when attempting to retrieve a team’s history of events via API if an application does not exist with a matching ID Addressed an issue where Admin level users are able to delete themselves Resolved an issue where Automated Defect Creation through Azure may not create defects
To view a complete list of changes and updates, including prior releases, please view the 3.X Version Feature Changes list. 3.6March 2024 | Note |
|---|
Upgrade Migration Notifications Users must be on version 3.5 to upgrade to 3.6. Users interested in migrating to 3.6 from 2.X must upgrade to 2.8.9.1first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Kafka changes. For REST API updates, refer to the Change Log.
|
Helm Key UpdatesAddressed Reported Issues SAML user with global admin role cannot access Queue Management User may not be able to select the Components and/or Affect versions when attempting to create a Defect tracker for Jira After uploading a file to the Application page, the UI does not reflect the new file
3.5January 2024 | Note |
|---|
Upgrade Migration Notifications Users must be on version 3.4.2 to upgrade to 3.5. Users interested in migrating to 3.5 from 2.X must upgrade to 2.8.9.1first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Kafka changes. For REST API updates, refer to the Change Log.
|
Helm Key UpdatesTo view a complete list of changes and updates, including prior releases, please view the 3.X Version Feature Changes list. Addressed Reported Issues Issue | Resolution |
|---|
When a user performs a Vulnerability Search API call using an invalid value, ThreadFix returns a “success=true” status with a blank message. | This issue has been addressed in 3.5, invalid values will return a “Vulnerability ID not found” message. | API calls for deleted or invalid IDs return a success message. | This issue has been addressed in 3.5. | On SQL Server, when exporting a Vulnerability Search CSV, the user receives an error. | This issue has been addressed in 3.5. | A Vulnerability Search API export returns different data each time it is performed regardless of filter settings. | This issue has been addressed in 3.5. | Some Veracode SCA findings may import with duplicate IDs of other findings rather than unique IDs. | This issue has been addressed in 3.5. |
3.4.2November 2023 | Note |
|---|
Upgrade Migration Notifications Users must be on version 3.4 to upgrade to 3.4.2. Users interested in migrating to 3.4.2 from 2.X must upgrade to 2.8.9.1first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Kafka changes. For REST API updates, refer to the Change Log.
|
Helm Key UpdatesThe ability to manually adjust a vulnerability’s /wiki/spaces/T3D/pages/2502658381 window has been reinstated Performance improvement for the Defect Reporter to Application Defect Tracker Mapping process ThreadFix MSSQL mappings update Checkmarx One available for Remote Provider and proxy settings Security improvements
To view a complete list of changes and updates, including prior releases, please view the 3.X Version Feature Changes list. Addressed Reported Issues Issue | Resolution |
|---|
MS SQL Server vulnerabilities display the incorrect Severity level. | This issue has been addressed in 3.4.2. | Customize Scanner Vulnerability Types Scanner Vulnerability Mapping may not update severities correctly. | This issue has been addressed in 3.4.2. | The ‘Tag’ field does not display when creating a new ticket in Azure DevOps. | This issue has been addressed in 3.4.2. | The Scan event messages in the History page displays the date with a UTC Time Zone rather than the user’s Local Time Zone. | This issue has been addressed in 3.4.2. | Issue where after a user updates the Default LDAP Role settings in ThreadFix, the login page may not respect default settings. | This issue has been addressed in 3.4.2. | Issue where a users name that has been updated in the User Management page may not reflect onto the user Login page. | This issue has been addressed in 3.4.2. | Issue where the Vulnerability Search API exports may provide different results each time run. | This issue has been addressed in 3.4.2. | Issue where a Remote Provider will not be created if the user attempts to use a previously entered a name for it that was submitted but not allowed to complete the creation process by exiting the modal before successful completion. | This issue has been addressed in 3.4.2. | Performance improvement for the BlackDuck Remote Provider creation process, addressing an issue where it may timeout. | This issue has been addressed in 3.4.2. | SAML login fails if a username includes invalid characters. | This issue has been addressed in 3.4.2. |
3.4October 2023 Important Integration Support Notifications Reminder: As of ThreadFix version 3.4, integration support is discontinued for Bugzilla (ver 4.x & 5.x), IBM ClearQuest, and VersionOne ThreadFix 3.4 supports MySQL 8 and is not backwards compatible to 5.7. Users will need to upgrade their database to MySQL 8 when upgrading to ThreadFix 3.4. Jira has deprecated and removed certain endpoints as of version 9.0, in order to maintain proper functionality with ThreadFix, it is recommended to upgrade to 3.4 AppScan Enterprise identified and resolved an issue where some vulnerabilities reported finding details for multiple issue types as a single concatenated string via the AppScan API. In this instance ThreadFix would ingest this data as if it was legitimate which could cause some display and merging issues if the instance of AppScan Enterprise in use is a version subject to this misbehavior. HCL has informed our impacted clients that the issues have been resolved; clients should prioritize updating their AppScan Enterprise instance to the latest HCL patch prior to updating ThreadFix.
| Note |
|---|
Upgrade Migration Notifications Users must be on version 3.3/ 3.3.1/ 3.3.2/ 3.3.3 / 3.3.4 to upgrade to 3.4. Users interested in migrating to 3.4 from 2.X must upgrade to 2.8.9 first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Kafka changes For REST API updates, refer to the Change Log
|
Helm Key UpdatesThreadFix has been updated to support MySQL 8 database CheckmarxOne has been added as a new Remote Provider Qualys WAS results now display more information for users to review CWE 16 behavior has been adjusted as many scanning tools provide CWE 16 as a catch all for vulnerabilities that are not specifically software in nature: It’s been observed through repeated testing that a more appropriate path for ThreadFix is to treat all SAST, DAST, IAST, and Mobile findings as unmergeable if they are classified as CWE 16. As of 3.4 ThreadFix will no longer permit merging in those instances. SCA/Dependency finding types will still merge as before as CWE is not a component of the merge logic for those findings
In preparation for ThreadFix SaaS - we have updated our Allowed and Blocked file types. Below are the current allowed file types that can be uploaded as scans: .csv .fpr .json .nessus .ozasmt .xml
Security updates Several minor UI updates
To view a complete list of changes and updates, including prior releases, please view the 3.X Version Feature Changes list. Addressed Reported Issues Issue | Resolution |
|---|
Findings show a CWE Number instead of a name. | This issue has been addressed in 3.4. | The Last Import Attempt Status does not update for Netsparker Enterprise app after a successful import. | This issue has been addressed in 3.4. | Issue where the user may not be able to view a defect from the Vulnerability Detail page, resulting in an error. | This issue has been addressed in 3.4. | Issue where not all Pen Test teams would display in the Identity Management page. | This issue has been addressed in 3.4. | Issue where if a Team is deleted in the Portfolio page and a newly created Team with the same name is created with an application, the previously deleted Team name may appear on the UI. | This issue has been addressed in 3.4. |
3.3.4August 2023 | Warning |
|---|
Integration Support Notifications As of ThreadFix version 3.4, integration support for Bugzilla (ver 4.x & 5.x), IBM ClearQuest, and VersionOne will be discontinued. ThreadFix currently supports MySQL up to version 5.7, the future release of ThreadFix 3.4 will support MySQL 8 and will not be backwards compatible to 5.7. Users will need to upgrade their database to MySQL 8 when upgrading to ThreadFix 3.4. Jira has deprecated and removed certain endpoints as of version 9.0, in order to maintain proper functionality with ThreadFix, it is recommended to upgrade to 3.3.4.
|
| Note |
|---|
Upgrade Migration Notifications Users must be on version 3.3/3.3.1/ 3.3.2/3.3.3 to upgrade to 3.3.4. Users interested in migrating to 3.3.4 from 2.X must upgrade to 2.8.8.5 first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Kafka changes. For REST API updates, refer to the Change Log.
|
Helm Key UpdatesTo view a complete list of changes and updates, including prior releases, please view the 3.X Version Feature Changes list. Addressed Reported Issues Issue | Resolution |
|---|
Qualys applications with over 100 open vulnerabilities do not automatically paginate scan results. | This issue has been addressed in 3.3.4. | User receives a NullPointerException error when trying to update an application, via the Update Application API, containing at least one unmapped vulnerability. | This issue has been addressed in 3.3.4. | ThreadFix’s integration with Black Duck ingests invalid Finding CVE data. | This issue has been addressed in 3.3.4. | For Acunetix 360 and Netsparker Enterprise, if the application is renamed on the scanner, the existing RemoteProviderApplication row is discarded. This occurs despite the nativeId value persisting. | This issue has been addressed in 3.3.4. | Error addressed when a user tries to edit a Jira defect tracker using a new longer API token. | This issue has been addressed in 3.3.4. | When creating a JIRA defect Tracker, the following error message is received:
“Failure. Message was : ThreadFix encountered an error and could not complete the request. Please check the Error Messages page or server logs for more details.” | This issue has been addressed in 3.3.4. | When a Fortify on Demand microservice is scanned, it registers more vulnerabilities than actually exist. | This issue has been addressed in 3.3.4. |
3.3.3July 2023 | Warning |
|---|
Integration Support Notifications As of ThreadFix versions 3.4, integration support for Bugzilla (ver 4.x & 5.x), IBM ClearQuest, and VersionOne will be discontinued. ThreadFix currently supports MySQL up to version 5.7, the future release of ThreadFix 3.4 will support MySQL 8 and will not be backwards compatible to 5.7. Users will need to upgrade their database to MySQL 8 when upgrading to ThreadFix 3.4. Jira has deprecated and removed certain endpoints as of version 9.0, in order to maintain proper functionality with ThreadFix, it is recommended to upgrade to 3.3.3.
|
| Note |
|---|
Upgrade Migration Notifications Users must be on version 3.3/ 3.3.1/ 3.3.2 to upgrade to 3.3.3 Users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Kafka changes. For REST API updates, refer to the Change Log.
|
Helm Key UpdatesImprovement to Vulnerability Detail page display of Findings Comments Improvement for scanning of Fortify XML files, removing invalid characters that may impede the scanning process Performance enhancements UI Improvements Security updates
To view a complete list of changes and updates, including prior releases, please view the 3.X Version Feature Changes list. Addressed Reported Issues Issue | Resolution |
|---|
LDAP user group membership not validated/synced on login. | This issue has been addressed in 3.3.3 | User receivers an “Invalid username/password combination” error when attempting to gather collections from a defect tracker in Azure DevOps. | This issue has been addressed in 3.3.3 | Under certain user configurations, importing Contrast Remote Provider findings may fail and provide a “Failed during remote provider import” error. | This issue has been addressed in 3.3.3 |
3.3.2May 2023 | Warning |
|---|
Integration Support Notifications As of ThreadFix versions 3.4, integration support for Bugzilla (ver 4.x & 5.x), IBM ClearQuest, and VersionOne will be discontinued ThreadFix currently supports MySQL up to version 5.7, the future release of ThreadFix 3.4 will support MySQL 8 and will not be backwards compatible to 5.7. Users will need to upgrade their database to MySQL 8 when upgrading to ThreadFix 3.4. Jira has deprecated and removed certain endpoints as of version 9.0, in order to maintain proper functionality with ThreadFix, it is recommended to upgrade to 3.3.2
|
| Note |
|---|
Upgrade Migration Notifications Users must be on version 3.3 or 3.3.1 to upgrade to 3.3.2. Users interested in migrating to 3.3.2 from 2.X must upgrade to 2.8.8.3 first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Kafka changes For REST API updates, refer to the Change Log
|
Helm Key UpdatesIssue addressed where users may not be able to upgrade to 3.X if specific data exists in the ChannelVulnerability table for Burp UI performance enhancements Microservice Project support added for Fortify on Demand Security updates
Addressed Reported Issues Issue | Resolution |
|---|
When submitting a new defect through the Azure DevOps / TFS defect tracker, the Area and Iteration drop-downs do not display set default values and cannot be edited. | This issue has been addressed in 3.3.2. | Unmapped Qualys WAS Findings are automatically upgraded/downgraded to a Severity level of 3 (Medium) and without a channel vulnerability name. | This issue has been addressed in 3.3.2. | ThreadFix allowing multiple scans without an Updated Date if there is a prior scan present containing an UpdatedDate. | This issue has been addressed in 3.3.2. | .threadfix file exports from the Assessment tab with incorrect Finding descriptions. | This issue has been addressed in 3.3.2. | Date displayed in the Status section of Vulnerability Details do not reflect a user’s local time zone. | This issue has been addressed in 3.3.2. | User receives a "Jira Credentials are invalid" error when authenticating with Atlassian’s newly implemented longer API tokens. | This issue has been addressed in 3.3.2. | SAML settings prevents System Settings page from updating/saving. | This issue has been addressed in 3.3.2. | Email notifications fail to send. | This issue has been addressed in 3.3.2. |
3.3.1February 2023 Note to users, ThreadFix currently supports MySQL up to version 5.7, the future release of ThreadFix 3.4 will support MySQL 8 and will not be backwards compatible to 5.7. Users will need to upgrade their database to MySQL 8 when upgrading to ThreadFix 3.4. | Note |
|---|
Users must be on version 3.2 or 3.3 to upgrade to 3.3.1. Users interested in migrating to 3.3.1 from 2.X must upgrade to 2.8.8 first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Note users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Posgresql changes |
Helm Key UpdatesImprovement of ThreadFix’s ability to identify and parse Fortify SCC external lists and filters to more accurately mark findings Improved ThreadFix upgrade migration automation to have better error handling and recovery
To view a complete list of changes and updates, including prior releases, please view the 3.X Version Feature Changes list. 3.3January 2023 | Note |
|---|
Users must be on version 3.2 to upgrade to 3.3. Users interested in migrating to 3.3 from 2.X must upgrade to 2.8.8 first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Note users installing or upgrading from prior versions of 3.X with Helm should be aware of the required Helm value and Posgresql changes. |
Helm Key Updates / Version Feature ChangesNew versions of ThreadFix may deprecate, remove, and/or reintroduce features. To view a list of feature changes please see below: Ingestion EnhancementsThreadFix File format now supports CVSS score values for both ingestion and export Fortify SSC/FoD/SCA imports have improved filter parsing to support more custom filters from Microfocus Fortify on Demand now supports dependency findings Acunetix enhanced false positive support Contrast findings support greater specificity in filtering on finding types based on finding data Added Scan Agent configuration support for AppScan Standard and WebInspect allowing custom configuration for these scan agents SonarQube integration has been updated to support changes in their API
System EnhancementsCreated UI driven customization for report caching times Added OWASP Top 10 2021 report API support added for custom severity name Created a bulk-export for all unmapped vulnerability types to CSV file Reintroduced Scan File Retention customization to the ThreadFix 3 architecture Reintroduced LDAP linked SAML Authorization to the ThreadFix 3 architecture The following Global FPR Filter Set API REST calls have been reintroduced: Additional bug fixes and security enhancements
Removed Features Addressed Reported Issues Issue | Resolution |
|---|
When installing ThreadFix with Helm, issues occur following changes made to the Helm charts. | It is recommended to not make any edits or changes to the Helm charts in order to avoid undesired performance. Any necessary changes should be done through the value files. | Following changes in the K8 APIs, installing or upgrading ThreadFix on Kubernetes versions 1.25 or newer will fail. | Resolved in ThreadFix 3.3. | Importing LDAP users fails if any user have Title fields containing over 60 characters. | The limit has been increased to 128. | In some instances, ThreadFix license expiration reminders can repeatedly post to the logs and create performance issues. | The frequency of reminders has been adjusted to once per user login. | A manually closed vulnerability may be marked as “re-opened” if a scan containing the open vulnerability is uploaded from a date prior to when it was manually closed. | ThreadFix will not mark a manually closed vulnerability as having been re-opened from an uploaded scan preceding the vulnerability having been manually closed. |
3.2| Warning |
|---|
October 2022 - Known Issue Warning: Following changes in the K8 APIs, installing or upgrading ThreadFix on Kubernetes versions 1.25 or newer will fail. This issue will be addressed in the next ThreadFix release. |
September 2022 | Note |
|---|
Users interested in migrating to 3.2 from 2.X must upgrade to 2.8.7 first, then contact the Coalfire Support Portal to continue with the 2.X to 3.X Migration process. Users upgrading from 3.1.2 please view the expandable note below before upgrading. |
In ThreadFix 3.2, Minio requires the Minio secret data to contain the keys “rootUser” and “rootPassword” instead of “secretKey” and “accessKey”. When attempting an upgrade, some users may encounter the following error: | Code Block |
|---|
Error: UPGRADE FAILED: template: threadfix/charts/minio/templates/secrets.yaml:14:15: executing "threadfix/charts/minio/templates/secrets.yaml" at <include "minio.root.username" .>: error calling include: template: threadfix/charts/minio/templates/_helpers.tpl:208:8: executing "minio.root.username" at <include "minio.getValueFromSecret" (dict "Namespace" .Release.Namespace "Name" (include "minio.fullname" .) "Length" 20 "Key" "rootUser")>: error calling include: template: threadfix/charts/minio/templates/_helpers.tpl:198:28: executing "minio.getValueFromSecret" at <b64dec>: invalid value; expected string |
This error can be resolved by manually editing the Minio secret to change the data values to what is expected. | Code Block |
|---|
kubectl edit secret tf-minio |
Change the following: | Code Block |
|---|
apiVersion: v1
data:
secretkey: <secret-key-value>
accesskey: <access-key-value> |
To: | Code Block |
|---|
apiVersion: v1
data:
secretkey: <secret-key-value>
accesskey: <access-key-value>
rootUser: <access-key-value>
rootPassword: <secret-key-value> |
Once complete, perform the upgrade procedure once again. Helm Key Updates / Version Feature ChangesNew versions of ThreadFix may deprecate, remove, and/or reintroduce features. To view a list of feature changes please see below: Azure Dev Ops 2.X Feature Parity (3.X only) Integration Enhancements The following remote providers now ingest and store CVSS values: Acunetix 360, Black Duck, Netsparker, NowSecure, and WhiteHat Sentinel Source Checkmarx can now ingest additional scanner detail and scanner recommendations for findings  Image AddedContrast date management enhancements to provide greater accuracy on finding discovery dates Improved SonarQube severity mappings The maximum number of Defect Profiles that can be associated with a single defect tracker has been increased to 1024 Improvement to Fortify SCC findings filtering
To view a complete list including prior releases, please view the 3.X Version Feature Changes list. Addressed Reported Issues and Security Updates Upgraded dependencies and images including Debian, Kafka, and ActiveMQ Fixed intermittent import errors with Acunetix 360/Netsparker WhiteHat API updates to support new requirements from WhiteHat Improvement to UI messaging indicating when all remote providers have been mapped Improvement to UI messaging indicating when an invalid scanId was used The ThreadFix UI Help button has been adjusted to now direct to the Coalfire Support Portal
Issue | Resolution |
|---|
Importing scan data from AsoC fails, displaying the following error message: “RestIOException: Invalid response from ASoC while fetching last scan date.” | Resolved ASoC integration errors on import | A user without read-access could view all policy data for an application | The Policies tab in ThreadFix has been updated to address the information disclosure | A vulnerability’s open and close dates will no longer shift with new scan uploads unless a reopen or close event occurs | Resolved scan delete error if it includes findings that belong to vulnerabilities that have been closed and reopened multiple times | When trying to update Jira Defect Tracker integration credentials, a 403 error is received with the following message: “Failure. Message was : The defect tracker URL is not valid." | Resolved JIRA connection issue | "You don't have permission for this team." error is received when attempting to move an application to another team using the Update Application API even with an Administrator Global role | The Update Application API has been updated to address the permissions error, allowing the application to be successfully moved | User unable to save an LDAP-linked SAML configuration, receiving a “Display Name Config Not Found” error | This issue has been addressed in 3.2 | Threadfix files incorrectly export with a filename of null instead of the associated application’s name | A fix has been provided to ensure the Threadfix files correctly export with associated application’s name | Occasionally Qualys WAS Finding Scan Details and Scan Recommendation sections do not import | Version 3.2 corrects the reported issue with the scanner details and recommendations properly displaying | Error importing Contrast cloud scans | Resolved imports failing for certain Ruby applications |
3.1.2May 2022 Helm Key Update Version Feature Changes New versions of ThreadFix may deprecate, remove, and/or reintroduce features. To view a list of feature changes please see below: To view a complete list including prior releases, please view the 3.X Version Feature Changes list. 3.1.1April 2022 | Warning |
|---|
The National Vulnerability Database has identified a high risk exploit, Spring4Shell, which affects applications running Tomcat as a WAR deployment. For more information refer to CVE-2022-22965. In response Coalfire has tested ThreadFix to assess risk and mitigation options and recommends users update to ThreadFix version 3.1.1 to mitigate risk of exposure and provide security enhancements. |
| Note |
|---|
Migration from 2.8.5.1 to 3.1.1 is currently not supported. Users interested in migrating to 3.1.1 must upgrade to 2.8.6 first then continue with the |
2.X to 3.X Migration Key Updates |
