

We are also monitoring further development of the story. We are continuing to test our services to see whether they are vulnerable, as a result of using third party components, and if/where applicable, take the necessary actions. Upsource – Fix was released in version #20 on 13th of December 2021.Floating license server – Fix was released in version #30211 on 11th of December 2021.JetBrains Account – Fix was released on 10th of December 2021.Code With Me – Fix was released on 13th of December 2021 (only jitsi which is used for calls was affected).YouTrack InCloud – Fix was released on 10th of December 2021.Details for both Hub and YouTrack: JT-67582. YouTrack Standalone – Fix was released in version #200 on 14th of December 2021.Hub – Fix was released in version #203 on 13th of December 2021.All IntelliJ platform based IDEs – Not affected.Following is the list of already audited products and their status: We have run an audit of the applications that use log4j and have upgraded to 2.15.0 where necessary. We immediately took action to mitigate any potential impacts on our applications and systems.

If you want to know more, checkout the SonarQube docker page.Similar to the rest of the industry, we became aware on the 10th of December 2021 of the Remote Code Execution vulnerability CVE-2021-44228 in the popular Java logging library log4j (all versions between 2.0 and 2.14.1 are vulnerable). Please note that this setup is not recommended for production. It seems that this project needs some attention. If all goes well, you've just created your first report and can access it on localhost on port 9000! Because the local SonarQube server stores every analysis in an internal H2 database you can even see what has changed since the last run. Starting the SonarQube server will take several minutes.Īfter it has started, you can generate a sonar report of your maven application with the followng command: mvn sonar:sonar To start a SonarQube instance you run the following command: docker run -d -name sonarqube -p 9000:9000 -p 9092:9092 sonarqube Luckily, it's now very easy to get your own SonarCube server running.īasically you only need a docker installation and a few simple steps.

I recently wanted to do some source code analysis and found it difficult to find a good eclipse plugin.
