Improper Verification of Cryptographic Signature Affecting rage-encryption-bash-completion package, versions <0.9.2+0-150500.3.3.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.23% (15th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES155-RAGEENCRYPTIONBASHCOMPLETION-5962521
  • published13 Oct 2023
  • disclosed12 Oct 2023

Introduced: 12 Oct 2023

CVE-2023-42811  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 rage-encryption-bash-completion to version 0.9.2+0-150500.3.3.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rage-encryption-bash-completion package and not the rage-encryption-bash-completion package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1