Описание
Security update for rage-encryption
This update for rage-encryption fixes the following issues:
-CVE-2023-42811: chosen ciphertext attack possible against aes-gcm (bsc#1215657)
- update vendor.tar.zst to contain aes-gcm >= 0.10.3
-
Update to version 0.9.2+0:
- CI: Ensure
aptrepository is up-to-date before installing build deps - CI: Build Linux releases using
ubuntu-20.04runner - CI: Remove most uses of
actions-rsactions
- CI: Ensure
-
Update to version 0.9.2+0:
- Fix changelog bugs and add missing entry
- Document
PINENTRY_PROGRAMenvironment variable - age: Add
Decryptor::new_async_buffered - age:
impl AsyncBufRead for ArmoredReader - Pre-initialize vectors when the capacity is known, or use arrays
- Use
PINENTRY_PROGRAMas environment variable forpinentry - Document why
impl AsyncWrite for StreamWriterdoesn't loop indefinitely - cargo update
- cargo vet prune
- Migrate to
cargo-vet 0.7 - build(deps): bump svenstaro/upload-release-action from 2.5.0 to 2.6.1
- Correct spelling in documentation
- build(deps): bump codecov/codecov-action from 3.1.1 to 3.1.4
- StreamWriter AsyncWrite: fix usage with futures::io::copy()
- rage: Use
Decryptor::new_buffered - age: Add
Decryptor::new_buffered - age:
impl BufRead for ArmoredReader - Update Homebrew formula to v0.9.1
- feat/pinentry: Use env var to define pinentry binary
-
Update to version 0.9.1+0:
- ssh: Fix parsing of OpenSSH private key format
- ssh: Support
aes256-gcm@openssh.comciphers for encrypted keys - ssh: Add
aes256-gcm@openssh.comcipher to test cases - ssh: Extract common key material derivation logic for encrypted keys
- ssh: Use associated constants for key and IV sizes
- ssh: Add test cases for encrypted keys
-
Add shell completions for fish and zsh.
Список пакетов
SUSE Linux Enterprise Module for Basesystem 15 SP5
openSUSE Leap 15.5
Ссылки
- Link for SUSE-SU-2023:4060-1
- E-Mail link for SUSE-SU-2023:4060-1
- SUSE Security Ratings
- SUSE Bug 1215657
- SUSE CVE CVE-2023-42811 page
Описание
aes-gcm is a pure Rust implementation of the AES-GCM. Starting in version 0.10.0 and prior to version 0.10.3, in the AES GCM implementation of decrypt_in_place_detached, the decrypted ciphertext (i.e. the correct plaintext) is exposed even if tag verification fails. If a program using the `aes-gcm` crate's `decrypt_in_place*` APIs accesses the buffer after decryption failure, it will contain a decryption of an unauthenticated input. Depending on the specific nature of the program this may enable Chosen Ciphertext Attacks (CCAs) which can cause a catastrophic breakage of the cipher including full plaintext recovery. Version 0.10.3 contains a fix for this issue.
Затронутые продукты
Ссылки
- CVE-2023-42811
- SUSE Bug 1215654