Skip to content
Noroxi
CVE-2016-6313· NVD / CVE Program· CNA redhat

The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1

The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easier for attackers to obtain the values of 160 bits by leveraging knowledge of the previous 4640 bits.

MediumCVSS 5.3 · v3.0—No exploit Fix available
Published
Dec 13, 2016
Updated
Jun 16, 2026
EPSS
3.6% · 89th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.6%

Affected systems

VendorProduct
gnupglibgcrypt
gnupggnupg
debiandebian linux
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux12.04
  • canonical ubuntu linux14.04
  • canonical ubuntu linux16.04
  • debian debian linux8.0
  • gnupg gnupgup to 1.4.14 inclusive
  • gnupg libgcryptup to 1.5.3 inclusive
  • gnupg libgcrypt1.6.0
  • gnupg libgcrypt1.6.1
  • gnupg libgcrypt1.6.2
  • gnupg libgcrypt1.6.3
  • gnupg libgcrypt1.6.4
  • gnupg libgcrypt1.6.5
  • gnupg libgcrypt1.7.0
  • gnupg libgcrypt1.7.1
  • gnupg libgcrypt1.7.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.4libgcryptbefore 1.7.0-r11.7.0-r1
Debian:12gnupg1before 1.4.21-11.4.21-1
Debian:12libgcrypt20before 1.7.3-11.7.3-1
Debian:7gnupgbefore 1.4.12-7+deb7u81.4.12-7+deb7u8
Debian:7libgcrypt11before 1.5.0-5+deb7u51.5.0-5+deb7u5
Debian:8gnupgbefore 1.4.18-7+deb8u21.4.18-7+deb8u2
Debian:8libgcrypt20before 1.6.3-2+deb8u21.6.3-2+deb8u2
openSUSE:Tumbleweedlibgcryptbefore 1.7.3-1.31.7.3-1.3
Red Hat:enterprise_linux:6::clientlibgcryptbefore 0:1.4.5-12.el6_80:1.4.5-12.el6_8
Red Hat:enterprise_linux:6::clientlibgcrypt-debuginfobefore 0:1.4.5-12.el6_80:1.4.5-12.el6_8
Red Hat:enterprise_linux:6::clientlibgcrypt-develbefore 0:1.4.5-12.el6_80:1.4.5-12.el6_8
Red Hat:enterprise_linux:7::clientlibgcryptbefore 0:1.5.3-13.el7_3.10:1.5.3-13.el7_3.1
Red Hat:enterprise_linux:7::clientlibgcrypt-debuginfobefore 0:1.5.3-13.el7_3.10:1.5.3-13.el7_3.1
Red Hat:enterprise_linux:7::clientlibgcrypt-develbefore 0:1.5.3-13.el7_3.10:1.5.3-13.el7_3.1
SUSE:Linux Enterprise Desktop 12 SP1libgcryptbefore 1.6.1-16.33.11.6.1-16.33.1
SUSE:Linux Enterprise Software Development Kit 11 SP4libgcryptbefore 1.5.0-0.22.11.5.0-0.22.1

Other highest-scoring records for the same primary product.

  • CVE-2021-33560Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel att
    31Monitor
  • CVE-2021-3345_gcry_md_block_write in cipher/hash-common.c in Libgcrypt version 1.9.0 has a heap-based buffer overflow when the digest final function sets
    31Monitor
  • CVE-2018-6829cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers t
    31Monitor
  • CVE-2017-0379Libgcrypt before 1.8.1 does not properly consider Curve25519 side-channel attacks, which makes it easier for attackers to discover a secret
    31Monitor
  • CVE-2017-7526libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left
    28Monitor
  • CVE-2026-41989Libgcrypt before 1.12.2 sometimes allows a heap-based buffer overflow and denial of service via crafted ECDH ciphertext to gcry_pk_decrypt.
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:libgcrypt1.7.0-r1 · Alpine:v3.4Package registry (OSV)
debian:gnupg1.4.12-7+deb7u8 · Debian:7Package registry (OSV)
debian:gnupg11.4.21-1 · Debian:12Package registry (OSV)
debian:libgcrypt111.5.0-5+deb7u5 · Debian:7Package registry (OSV)
debian:libgcrypt201.7.3-1 · Debian:12Package registry (OSV)
opensuse:libgcrypt1.7.3-1.3 · openSUSE:TumbleweedPackage registry (OSV)
red hat:libgcrypt0:1.4.5-12.el6_8 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:libgcrypt-debuginfo0:1.4.5-12.el6_8 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:libgcrypt-devel0:1.4.5-12.el6_8 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
suse:libgcrypt1.6.1-16.33.1 · SUSE:Linux Enterprise Desktop 12 SP1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records