As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Threat Intelligence Exchange Server 3.x Known Issues
Technical Articles ID:
KB91389
Last Modified: 2023-07-26 04:35:26 Etc/GMT
Environment
Threat Intelligence Exchange (TIE) Server 3.x
Summary
Recent updates to this article
Date
Update
July 25, 2023
Added TIE Server 3.0.3 Hotfix 4 release details in the "Product release information" section.
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Product release information
Version
Release date
TIE Server 3.0.3 Hotfix 4 (GA)
July 25, 2023
TIE Server 3.0.3 (GA)
February 8, 2022
TIE Server 3.0.1 Hotfix 4 (GA)
December 30, 2021
TIE Server 3.0.1 (GA)
September 8, 2019
TIE Server 3.0.0 Hotfix 1 (GA)
November 12, 2019
TIE Server 3.0.0 (GA)
October 8, 2019
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site.
Contents
Click to expand the section you want to view:
Reference
Number
Related
Article
Found
Version
Resolved
Version
Issue Description
TIESERVER-10577
-
3.0.0
3.0.3
Issue: Upgraded OpenSSL library version to 1.0.2y to address the vulnerability CVE-2020-1971.
TIESERVER-11537
3.0.0
3.0.3
Issue: Upgraded Sudo library version to 1.8.6p3-32 to address the vulnerability CVE-2021-3156.
TIESERVER-11534
3.0.0
3.0.3
Issue: Upgraded Network Security Services library version to 3.44.0-12.mlos2.x86_64.rpm to address the vulnerability CVE-2021-43527.
Issue: When you try to upgrade to TIE Server 3.0.1.165, the upgrade fails.
The error below is recorded in the tieserver-3.0.1-xxx.log file (/var/log/):
package nginx-filesystem-1:1.21.0-1.mlos2.noarch (which is newer than nginx-filesystem-1:1.19.1-1.mlos2.noarch) is already installed
Issue: Secondary or Reporting Secondary server upgrade fails when replication reset is tried after the Primary server is upgraded.
Resolution: This issue is resolved in TIE 3.0.0 Hotfix 1. If you've upgraded your server to the TIE 3.0.0 GA version and experience the issue, see the related article.
TIESERVER-7371
-
3.0.0
3.0.0 Hotfix 1
Issue: When you run an "External Reputation" query, you still see the external reputation score in the "TIE Reputations" columns.
Resolution: This issue is resolved in TIE 3.0.0 Hotfix 1.
Issue: A TIE Server upgrade fails when a custom index is added to the database.
Workaround: See the related article for details.
TIESERVER-7037
-
3.0.0
-
Issue: You see the following error after you upgrade to TIE 3.0.0: "Not Available." The status is listed as a First Agent Guid in the 'Endpoints with most new unknown files' panel. The panel is in the 'TIE Server Priority Unknown Dashboards'.
Cause: This behavior is expected. You see this behavior when files have a First contact date that's before the upgrade to 3.0.0, and the Latest Metadata update date is after the upgrade. (They have a Priority value, but no First Agent value). The panel shows Files whose First execution date is within a month, so "Not Available" doesn't appear as First Agent Guid after one month.
NOTE: After you upgrade to version 3.0.0, the existing files don't have a value for the First Agent attribute.
Resolution: There's no solution for TIE 3.0.0. This issue stops occurring one month from the date of the TIE Server upgrade.
-
-
2.3.0
-
Issue: Unattended deployment doesn't allow multiple DNS servers. You can configure only one preferred DNS server in the Server Deployment extension.
Workaround: Deploy using a single DNS server. Then, after deployment, add alternative DNS servers through the reconfig-network script.
1205248
-
2.1.0
-
Issue: An error displays when you select some custom filters and the "Enterprise Reputation" column. Neither of the "Composite Reputation" columns display.
Issue: The TIE Server Deployment Extension page doesn't allow accented or double-byte characters in some fields.
Resolution: See the related article for details.
-
-
2.3.1
-
Issue: Some of the queries have summary totals that don't match the 'count of items.' You see this issue when you view items listed and the same query is drilled down.
Cause: The first query executed uses a different date format than the one executed when the drill-down is made.
