teamcityservice.exe version after upgrade
We recently upgraded our TeamCity server to version 2025.03 Build 186049. Our security team is saying that the TeamCityService.exe is flagged as being the 2019 version and having a vulnerability, and needs to be upgraded to at least version 2023. I either need to be able to show them that it is the correct file for the installed version, or it needs to be updated, so how do I know if this is the correct file for the installed version?
Please sign in to leave a comment.
There is a fix available for this situation. Please find the details in our documentation here: https://www.jetbrains.com/help/teamcity/known-issues.html#Incorrect+TeamCity+Server+Version+in+Windows
Mention to your security team they should properly evaluate the quality of their security products.
This one is clearly rubbish, as its using a registry key to determine the version, and when tou dona teamcity eeb update, the registry isn't updated.
There is a poweshell script that will sync the version, and shut up the “security” product.
Thank you Eric. I have run that script and let my security team know (I'm just waiting to hear back from them). I did notice something about that file though, and a few others… everything in the TeamCity/bin folder has a date modified of the date that I did the upgrade except for teamcity-server.bat, teamcity-server.sh, and TeamCityService.exe, they are all from 2020. Is that normal?
Normally, the files in TeamCity/bin are replaced during the upgrade process. You could download the tar.gz from here and replace anything not up to date. I show the following files/dates: