TIBCO Enterprise Administrator (TEA) 2.3.0 Hotfix 05 is now available.
book
Article ID: KB0079239
calendar_today
Updated On:
Products
Versions
TIBCO Enterprise Administrator (TEA)
2.3.0
Description
The customer will be able to download the Hotfix from the TIBCO Support Customer Portal Web UI using their username and password for the TIBCO Support Web page.Once logged on they can find the Hotfix under the Download Menu : AvailableDownloads/TEA/2.3.0/hotfix-05
For instructions on "How do TIBCO customers access Hot Fixes or Engineering Builds or customer-specific files" ., you can refer to Published Article 000022290 : https://support.tibco.com/s/article/hotfix
Please contact TIBCO Support if you have any problems finding or downloading this hotfix.
Listed below is a summary of updates included. Refer to the associated readme document for any additional information. ===================================================================================== Closed Issues in 2.3.0 HF-005 (This Release)
TEA-3250 Sensitive information was disclosed in the error messages of TIBCO Enterprise Administrator server.
TEA-3249 Sensitive information was disclosed in the HTTP response headers of TIBCO Enterprise Administrator server.
TEA-3247 The Referrer-Policy HTTP security header was not included in the response of TIBCO Enterprise Administrator server.
TEA-3237 The Python API did not handle the TeaParam value when FILE type was null.
TEA-3207 When you used the addprivilege operation on the TIBCO Enterprise Administrator shell, an error occurred after running the createrole command.
TEA-3145 The X-Frame-Options header was not included in the HTTP response of TIBCO Enterprise Administrator server.
TEA-3143 The "X-Content-Type-Options" HTTP header was missing from a TIBCO Enterprise Administrator.
TEA-3142 The "Content-Security-Policy" HTTP header was missing from a TIBCO Enterprise Administrator.
TEA-3140 There was an HTTP Verb Tampering attack vulnerability on the TIBCO Enterprise Administrator.
TEA-2952 TIBCO Enterprise Administrator did not expose the Transport Layer Security settings that helped in disabling or enabling specific cipher suites.