CVE-2022-45471 Email throttling was missed in JetBrains Hub before 2022.3.15181.

CVE-2022-45471 Email throttling was missed in JetBrains Hub before 2022.3.15181.

This issue was fixed in JetBrains Hub before 2022.3.15181. Unfortunately, the issue was not caught during the testing process before the release. If you are using the email feature in your project and getting the following message: “Throttling failed. Please try again later”, then update JetBrains Hub before 2022.3.15181 to avoid this issue.

For more details about this issue, see the email throttling bug report on GitHub.

TLS 1.2 support in JetBrains TeamCity

JetBrains TeamCity 8.1 and later support TLS 1.2 by default so you can connect to a remote server without having to install any additional software or set up a TLS 1.2-enabled server on your local machine.

However, if you are using JetBrains TeamCity with an older version of Java (Java 8 update 45 or earlier), then it is not possible to use TLS 1.2 with the currently supported protocol versions -- lower than the minimum version of Java required for JetBrains TeamCity. To work around this issue, you need to update Java on your local machine in order to allow the use of TLS 1.2 with lower protocol versions.

Update to JetBrains ReSharper (2019.2)

JetBrains ReSharper 2019.2 is the latest release of ReSharper that addresses this issue. It can be downloaded from the JetBrains website, where you will also find additional information about the issue and troubleshooting tips.

JetBrains Hub upgrade is not completed

JetBrains Hub upgrade is not completed. There might be a chance that the issue will be fixed in JetBrains Hub before 2022.3.15181, but it's too early to tell. If you are using the email feature in your project and getting the following message: “Throttling failed. Please try again later”, then update JetBrains Hub before 2022.3.15181 to avoid this issue.

References

Subscribe to CVE.news
Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe