A critical cryptographic vulnerability in Ribose RNP version 0.18.0 allows for the trivial decryption of public-key encrypted data, leading to a complete loss of confidentiality.

The flaw, categorized as CWE-330 (Use of Insufficiently Random Values), occurs because a refactoring error leaves the symmetric session key for Public-Key Encrypted Session Key packets as an all-zero byte array. This vulnerability is exploitable by an unauthenticated attacker who intercepts encrypted traffic.

The impact of this vulnerability is severe as it effectively negates the primary security function of the software: confidentiality. Any data encrypted using public-key methods in this version can be decrypted by unauthorized parties, potentially exposing sensitive communications, credentials, or proprietary information. With a CVSS score of 7.5, this high-severity flaw poses a significant risk to organizational data integrity and compliance requirements.

Immediate Action: Upgrade to RNP version 0.18.1 immediately, or revert to version 0.17.1 if 0.18.1 is not yet available for your specific distribution.

Proactive Monitoring: Review logs for unauthorized attempts to access or decrypt encrypted archives and monitor for any anomalous traffic patterns related to cryptographic operations.

Compensating Controls: If immediate patching is not possible, cease using public-key encryption features within the affected RNP version and prioritize the use of alternative secure communication channels that do not rely on the vulnerable PKESK implementation.

Public Exploit Available: Unknown

Given the total failure of encryption for public-key packets in RNP 0.18.0, organizations must treat this as a high-priority remediation task. Failure to update the software will leave all information protected by public-key encryption exposed to anyone with access to the encrypted packets. Ensure that all systems, including those bundling RNP such as Thunderbird, are updated to the secure versions as soon as they become available.