CVE-2017-0379 json
Libgcrypt before 1.8.1 does not properly consider Curve25519 side-channel attacks, which makes it easier for attackers to discover a secret…
published 2017-08-29 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-0733
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- libgcrypt20 Debian 14, Debian 13, Debian 12 1.7.9-1
debian advisories DEBIAN-CVE-2017-0379
- libgcrypt openSUSE Tumbleweed 1.9.4-1.2
opensuse advisories openSUSE-SU-2024:10941-1
- libgcrypt Alpine 3.6, Alpine 3.5, Alpine 3.4 1.7.9-r0
alpine advisories ALPINE-CVE-2017-0379
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-0379 updated cvss 4.4
libgcrypt: Missing input validation for X25519 curve
-
Red Hat Enterprise Linux 5 libgcrypt Red Hat Enterprise Linux 6 libgcrypt Red Hat Enterprise Linux 7 libgcrypt Red Hat Enterprise Virtualization 3 mingw-virt-viewer, mingw32-virt-viewer, mingw64-virt-viewernot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.51% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- n/a libgcrypt
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
debian.org
/security/2017/dsa-3959
vendor-advisory, patch, third-party-advisory
-
lists.debian.org
/debian-security-announce/2017/msg00221.html
mailing-list, patch, third-party-advisory
-
security-tracker.debian.org
/tracker/CVE-2017-0379
patch, third-party-advisory
-
securityfocus.com
/bid/100503
vdb-entry, third-party-advisory
- oracle.com /technetwork/security-advisory/cpujul2018-4258247.html
- oracle.com /technetwork/security-advisory/cpujan2019-5072801.html
-
securitytracker.com
/id/1041294
vdb-entry
- git.gnupg.org /cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=da780c8183cccc8f533c8ace8211ac2cb2bdee7b
-
eprint.iacr.org
/2017/806
mailing-list, third-party-advisory
- security.netapp.com /advisory/ntap-20180726-0002/
-
bugs.debian.org
/873383
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2017-0379
- NVD CVE-2017-0379
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.