Tech

What changed

The performance of applications utilizing X9.42 Diffie-Hellman (DH) key generation and validation functions has come under scrutiny. Specifically, operations involving excessively long keys or parameters can result in considerable slowdowns.

Functions such as DH_generate_key(), DH_check_pub_key(), DH_check_pub_key_ex(), and EVP_PKEY_public_check() are particularly affected, leading to potential Denial of Service (DoS) conditions.

Who is affected

Various applications and systems that rely on X9.42 DH key generation and validation are at risk. This includes:

Developers and organizations that implement cryptographic protocols using X9.42 DH standards may experience significant delays.

• Cryptographic libraries that include X9.42 DH functions.
• Enterprise applications that utilize these cryptographic methods for secure communications.
• Any system that relies on external sources for key parameters, increasing the risk of performance degradation.

What to do

To mitigate the risks associated with these performance issues, organizations should consider reviewing their implementation of X9.42 DH functions. This includes:

Implementing checks to limit the length of keys and parameters being processed.

• Regularly audit cryptographic implementations to ensure compliance with best practices.
• Consider alternative key generation methods if performance issues persist.
• Stay informed about updates and patches related to cryptographic libraries.

What changed

Atlassian has disclosed an improper authorization vulnerability affecting all versions of Confluence Data Center and Server. This flaw allows unauthenticated attackers to reset the Confluence instance and create a new administrator account.

Once an attacker gains administrative access, they can execute a range of actions that jeopardize the confidentiality, integrity, and availability of the system.

Who is affected

This vulnerability impacts various users and organizations utilizing Atlassian Confluence Data Center and Server, particularly those who have not yet applied security updates.

While Atlassian Cloud sites are not vulnerable, on-premises installations remain at risk.

• Organizations using Atlassian Confluence Data Center and Server.
• IT departments managing on-premises Confluence instances.
• Businesses relying on Confluence for collaboration and documentation.
• Users with administrative access to Confluence Data Center and Server.

What to do

It is crucial for affected organizations to assess their Confluence installations and apply any available patches or updates to mitigate this vulnerability.

Regular security audits and monitoring of access logs are recommended to detect any unauthorized activities.

• Review and update to the latest version of Confluence Data Center and Server.
• Implement strict access controls and monitoring for administrative accounts.
• Educate staff about security best practices related to system access.