Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-0379

libgcrypt: Missing input validation for X25519 curve

Overview

Published
29 Aug 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
8 OS packages
4 Linux distributions
Yes Fix available

Description

Libgcrypt before 1.8.1 does not properly consider Curve25519 side-channel attacks, which makes it easier for attackers to discover a secret key, related to cipher/ecc.c and mpi/ec.c.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Weakness: CWE-200

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 10 fixes

debian 5 releases · 1 package

fixed 5
libgcrypt20
debian fixes for CVE-2017-0379
ReleasePackageFixed in
11 libgcrypt20 1.7.9-1
12 libgcrypt20 1.7.9-1
13 libgcrypt20 1.7.9-1
14 libgcrypt20 1.7.9-1
9 libgcrypt20 1.7.6-2+deb9u2

echo 1 release · 1 package

fixed 1
libgcrypt20
echo fixes for CVE-2017-0379
ReleasePackageFixed in
libgcrypt20 1.7.9-1

openSUSE 1 release · 1 package

fixed 1
libgcrypt-cavs
openSUSE fixes for CVE-2017-0379
ReleasePackageFixed inAdvisory
Tumbleweed libgcrypt-cavs +6 1.9.4-1.2 openSUSE-SU-2024:10941-1

root.io debian 3 releases · 1 package

fixed 3
rootio-libgcrypt20
root.io debian fixes for CVE-2017-0379
ReleasePackageFixed in
11 rootio-libgcrypt20 1.7.9-1
12 rootio-libgcrypt20 1.7.9-1
13 rootio-libgcrypt20 1.7.9-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.