Rnp

In RNP version 0.18.0 a refactoring regression causes the symmetric session key used for Public-Key Encrypted Session Key (PKESK) packets to be left uninitialized except for zeroing, resulting in it always being an all-zero byte array. Any data encrypted using public-key encryption in this release can be decrypted trivially by supplying an all-zero session key, fully compromising confidentiality. The vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected. Root cause: Vulnerable session key buffer used in PKESK packet generation. The defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization logic inside `encrypted_build_skesk()` only randomized the key for the SKESK path and omitted it for the PKESK path.

Published: 2025-11-21T17:05:15.683Z
Updated: 2025-11-21T17:35:33.645Z

Ribose RNP before 0.16.3 sometimes lets secret keys remain unlocked after use.

Published: 2023-04-24T00:00:00.000Z
Updated: 2025-02-04T20:59:09.130Z

Ribose RNP before 0.16.3 may hang when the input is malformed.

Published: 2023-04-24T00:00:00.000Z
Updated: 2025-11-21T20:05:26.539Z

Ribose RNP before 0.15.1 does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than on the tin of the algorithm.

Published: 2023-04-21T00:00:00.000Z
Updated: 2025-02-04T21:22:34.496Z