Vulnerability in libgcrypt11 - Security Update

libgcrypt11 Updated 02 Oct 2025

Summary

23/08/2016
N/A
Yes i
Unrated
Not published

DLA-600-1: libgcrypt11 - security update. Affects libgcrypt11 versions < 1.5.0-5+deb7u5. Fixed in 1.5.0-5+deb7u5. 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 crypto library used in the Debian 7 Wheezy ecosystem. It provides various cryptographic algorithms and functions for secure communication and data protection. However, a weakness has been discovered in the random number generator of libgcrypt11.

Vulnerability Detail

The vulnerability, identified as CVE-2016-6313, stems from a bug in the mixing functions of Libgcrypt's random number generator. If an attacker manages to obtain 4640 bits from the RNG, they can easily predict the next 160 bits of output. While existing RSA keys are not weakened, the prediction of private keys from public information for DSA and Elgamal keys is also unlikely.

How To Fix

Minimum fixed version

1.5.0-5+deb7u5

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 →

Workaround

No specific workaround has been mentioned for this vulnerability.

Conclusion

In conclusion, libgcrypt11 in Debian 7 Wheezy is vulnerable to a weakness in its random number generator. Upgrading to version 1.5.0-5+deb7u5 or later is recommended to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libgcrypt11 →

Share this vulnerability

FAQ

libgcrypt11 is a crypto library used for cryptographic operations in the Debian 7 Wheezy ecosystem.

Existing RSA keys are not weakened by this vulnerability.

While it is unlikely, this vulnerability does not completely rule out the possibility of predicting private keys from public information for DSA and Elgamal keys.

To fix this vulnerability, upgrade the libgcrypt11 package to version 1.5.0-5+deb7u5 or later.

You can find more information about Debian LTS security advisories, including how to apply updates and frequently asked questions, at https://wiki.debian.org/LTS.

Related vulnerabilities

Recent vulnerabilities recorded for libgcrypt11.

How To Fix

Minimum fixed version

1.5.0-5+deb7u5

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