The following security-related issues are resolved in "product name" "version".
Highest severity of resolved issues: High
To learn about the different severity levels of security vulnerabilities, see What are security updates?
| Issue | Severity | Description |
|---|---|---|
| 447971 | High | Custom patroller encryption now implements Public key authentication using HTTPS. |
| 447963 | High | Stored Patroller passwords now use PBKDF2 encryption. |
| 447922 | High | Registering Patroller to Security Center now requires Security Center credentials that include the Patroller Register privilege. |
| 434549 | High | Updated the libxml2.dll package to version 2.14.5. |
| 345346 | High | Updated the freetype.dll package to version 2.13.3. |
| 434544 | Medium | Fixed CVE-2024-43485 (CWE-400) by removing an unused test project. |
| 345194 | Medium | All connections between Security Center and Patrollers are now encrypted by default. |
| 341714 | Medium | Updated all the IdentityModel libraries to 8.0.2.0 to prevent any security vulnerabilities from JSON Web Token Handler For the Microsoft .Net Framework 4.5 package. |
| 341713 | Medium | The azure-activedirectory-identitymodel-extensions-for-dotnet
is no longer used in the Patroller. |
| 341631 | Medium | Updated database queries that were vulnerable to SQL injection (CWE-89). |
| 339353 | Medium | Enabled FIPS-compliant encryption to store passwords. |
| 339454 | Low | Patroller now uses asymmetric encryption for password changes. |