CVE-2024-2236

The libgcrypt library provides general-purpose implementations of various cryptographic algorithms.

Security Fix(es):

• libgcrypt: vulnerable to Marvin Attack (CVE-2024-2236)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Additional Changes:

For detailed information on changes in this release, see the Rocky Linux 9.5 Release Notes linked from the References section.

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

The libgcrypt library provides general-purpose implementations of various cryptographic algorithms.

Security Fix(es):

• libgcrypt: vulnerable to Marvin Attack (CVE-2024-2236)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Additional Changes:

For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

• CVE-2024-2236: fix timing-based side-channel vulnerability in RSA implementation

• Synced to upstream plus ASN.1 patch
• Tested on AlmaLinux 9.5
• Fix CVE-2024-2236 (RHEL-34579)

• Synced to upstream plus ASN.1 patch
• Tested on AlmaLinux 9.5
• Fix CVE-2024-2236 (RHEL-34579)

• Synced to upstream plus ASN.1 patch
• Tested on AlmaLinux 9.5
• Fix CVE-2024-2236 (RHEL-34579)

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Libgcrypt: vulnerable to marvin attack. (CVE-2024-2236)

This update for libgcrypt, libgpg-error fixes the following issues:

Update libgcrypt to 1.12.1 (jsc#PED-15059):

• New and extended interfaces:

• Allow access to the FIPS service indicator via the new GCRYCTL_FIPS_SERVICE_INDICATOR control code.
• Make SHA-1 non-FIPS internally for the 1.12 API
• Add Dilithium (ML-DSA) support
• Support optional random-override and support byte string data

• Bug fixes:

• Use secure MPI in _gcry_mpi_assign_limb_space.
• Use CSIDL_COMMON_APPDATA instead of /etc on Windows.
• Apply a Kyber patch from upstream.
• Fix an edge case in Jent initialization.
• mceliece6688128f: Fix stack overflow crash on win64/wine

• Performance:

• Many performance improvements, new AVX512 implementations for modern CPUs.
• Add RISC-V Zbb+Zbc implementation of CRC.
• Add RISC-V vector cryptography implementation of GHASH, AES, SHA256 and SHA512
• Add AVX2 and AVX512 code paths to improve CRC.

For a full changelog, see: https://dev.gnupg.org/source/libgcrypt/history/master/;libgcrypt-1.12.0

Update libgpg-error to 1.58:

• New src/gpg-error.c (main): New command "fconcat".
• Rename src/spawn-posix.c (struct gpgrt_spawn_actions): Rename the field to ENVP.
• argparse: Use SYSCONFDIR for /etc.
• Update translations for Portugese, German
• src/estream.c (parse_mode): Fix parsing of "share". Set sysopen flag.
• syscfg: Add 64-bit Android arch.

These are all security issues fixed in the libgcrypt-devel-1.11.1-2.1 package on the GA media of openSUSE Tumbleweed.

Root has patched CVE-2024-2236 in the libgcrypt20 package for Root:Debian:12. Multiple fixed versions available.

Root has patched CVE-2024-2236 in the libgcrypt20 package for Root:Ubuntu:22.04. Multiple fixed versions available.

This update for libgcrypt, libgpg-error fixes the following issues:

Update libgcrypt to 1.12.1 (jsc#PED-15059):

• New and extended interfaces:

• Allow access to the FIPS service indicator via the new GCRYCTL_FIPS_SERVICE_INDICATOR control code.
• Make SHA-1 non-FIPS internally for the 1.12 API
• Add Dilithium (ML-DSA) support
• Support optional random-override and support byte string data

• Bug fixes:

• Use secure MPI in _gcry_mpi_assign_limb_space.
• Use CSIDL_COMMON_APPDATA instead of /etc on Windows.
• Apply a Kyber patch from upstream.
• Fix an edge case in Jent initialization.
• mceliece6688128f: Fix stack overflow crash on win64/wine

• Performance:

• Many performance improvements, new AVX512 implementations for modern CPUs.
• Add RISC-V Zbb+Zbc implementation of CRC.
• Add RISC-V vector cryptography implementation of GHASH, AES, SHA256 and SHA512
• Add AVX2 and AVX512 code paths to improve CRC.

For a full changelog, see: https://dev.gnupg.org/source/libgcrypt/history/master/;libgcrypt-1.12.0

Update libgpg-error to 1.58:

• New src/gpg-error.c (main): New command "fconcat".
• Rename src/spawn-posix.c (struct gpgrt_spawn_actions): Rename the field to ENVP.
• argparse: Use SYSCONFDIR for /etc.
• Update translations for Portugese, German
• src/estream.c (parse_mode): Fix parsing of "share". Set sysopen flag.
• syscfg: Add 64-bit Android arch.

This update for libgcrypt, libgpg-error fixes the following issues:

Update libgcrypt to 1.12.1 (jsc#PED-15059):

• New and extended interfaces:

• Allow access to the FIPS service indicator via the new GCRYCTL_FIPS_SERVICE_INDICATOR control code.
• Make SHA-1 non-FIPS internally for the 1.12 API
• Add Dilithium (ML-DSA) support
• Support optional random-override and support byte string data

• Bug fixes:

• Use secure MPI in _gcry_mpi_assign_limb_space.
• Use CSIDL_COMMON_APPDATA instead of /etc on Windows.
• Apply a Kyber patch from upstream.
• Fix an edge case in Jent initialization.
• mceliece6688128f: Fix stack overflow crash on win64/wine

• Performance:

• Many performance improvements, new AVX512 implementations for modern CPUs.
• Add RISC-V Zbb+Zbc implementation of CRC.
• Add RISC-V vector cryptography implementation of GHASH, AES, SHA256 and SHA512
• Add AVX2 and AVX512 code paths to improve CRC.

For a full changelog, see: https://dev.gnupg.org/source/libgcrypt/history/master/;libgcrypt-1.12.0

Update libgpg-error to 1.58:

• New src/gpg-error.c (main): New command "fconcat".
• Rename src/spawn-posix.c (struct gpgrt_spawn_actions): Rename the field to ENVP.
• argparse: Use SYSCONFDIR for /etc.
• Update translations for Portugese, German
• src/estream.c (parse_mode): Fix parsing of "share". Set sysopen flag.
• syscfg: Add 64-bit Android arch.

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: Fixed timing based side-channel in RSA implementation. (bsc#1221107)

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: timing-based side-channel flaw in RSA implementation can lead to decryption of RSA ciphertexts (bsc#1221107).

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: timing-based side-channel flaw in RSA implementation can lead to decryption of RSA ciphertexts (bsc#1221107).

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: timing-based side-channel flaw in RSA implementation can lead to decryption of RSA ciphertexts (bsc#1221107).

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: timing-based side-channel flaw in RSA implementation can lead to decryption of RSA ciphertexts (bsc#1221107).

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: timing-based side-channel flaw in RSA implementation can lead to decryption of RSA ciphertexts (bsc#1221107).

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: timing-based side-channel flaw in RSA implementation can lead to decryption of RSA ciphertexts (bsc#1221107).

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: Fixed timing based side-channel in RSA implementation (bsc#1221107)

This update for libgcrypt fixes the following issues:

• CVE-2024-2236: Fixed timing based side-channel in RSA implementation (bsc#1221107)

It was discovered that Libgcrypt had a timing-based side-channel flaw in its RSA implementation. A remote attacker could possibly use this issue to obtain sensitive information.