Vulnerability in libgcrypt11 - Elgamal Encryption Subkeys Leakage

libgcrypt11 Updated 02 Oct 2025

Summary

16/11/2014
N/A
Yes i
Unrated
Not published

DSA-3073-1: libgcrypt11 - security update. Affects libgcrypt11 versions < 1.5.0-5+deb7u2. Fixed in 1.5.0-5+deb7u2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

libgcrypt11 is a library used by various applications, including GnuPG 2.x, for cryptographic operations. It provides functions for secure encryption, decryption, and key management. The library is widely used in the Debian 7 ecosystem. However, a vulnerability has been discovered in the Elgamal encryption subkeys implementation, which could lead to the leakage of sensitive information.

Vulnerability Detail

The vulnerability in libgcrypt11 allows for the leakage of Elgamal encryption subkeys through a side-channel attack. This means that an attacker could potentially extract these subkeys by analyzing the physical characteristics of the system during cryptographic operations. The impact of this vulnerability is significant as it could compromise the confidentiality of encrypted data and potentially lead to unauthorized access to sensitive information.

How To Fix

Minimum fixed version

1.5.0-5+deb7u2

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libgcrypt11

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

The vulnerability in libgcrypt11 can lead to the leakage of Elgamal encryption subkeys, compromising the confidentiality of encrypted data. It is crucial to upgrade the libgcrypt11 package to the fixed version to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libgcrypt11 →

Share this vulnerability

FAQ

libgcrypt11 is a cryptographic library used by various applications for secure encryption, decryption, and key management.

The vulnerability allows for the leakage of Elgamal encryption subkeys, which could compromise the confidentiality of encrypted data and potentially lead to unauthorized access to sensitive information.

Applications using the libgcrypt11 library, such as GnuPG 2.x, are affected by this vulnerability.

To fix this vulnerability, it is recommended to upgrade the libgcrypt11 package to version 1.5.0-5+deb7u2 or later.

No specific workaround has been provided for this vulnerability. It is recommended to apply the fix by upgrading the libgcrypt11 package.

Related vulnerabilities

Recent vulnerabilities recorded for libgcrypt11.

How To Fix

Minimum fixed version

1.5.0-5+deb7u2

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libgcrypt11

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback