Memory-Cache Side-Channel Attack in libgcrypt: CVE-2018-0495 Vulnerability

libgcrypt Updated 02 Oct 2025

Summary

13/06/2018
N/A
Yes i
Medium
4.7

ALPINE-CVE-2018-0495: Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign functi... Affects libgcrypt versions < 1.8.3-r0. Fixed in 1.8.3-r0. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libgcrypt is a cryptographic library that provides a wide range of cryptographic functions, including encryption, decryption, and digital signatures. It is widely used in various applications for secure data handling. However, certain versions of libgcrypt are vulnerable to a memory-cache side-channel attack, specifically affecting ECDSA signatures, which can compromise the security of cryptographic operations.

Vulnerability Detail

The vulnerability, identified as CVE-2018-0495, allows an attacker to exploit a memory-cache side-channel attack on ECDSA signatures. This issue arises from the lack of blinding during the signing process in the _gcry_ecc_ecdsa_sign function. An attacker with access to the local machine or another virtual machine on the same physical host can potentially discover the ECDSA key, leading to unauthorized access and data breaches. The vulnerability affects libgcrypt versions prior to 1.7.10 and 1.8.x before 1.8.3.

How To Fix

Minimum fixed version

1.8.3-r0

This is the first release that contains the fix.

sudo apk add --upgrade libgcrypt

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

Workaround

As a temporary workaround, consider implementing additional security measures such as isolating sensitive operations to dedicated hardware or using alternative cryptographic libraries that are not affected by this vulnerability until an update can be applied.

Conclusion

CVE-2018-0495 represents a significant security risk for applications using vulnerable versions of libgcrypt. It is crucial to update to the patched version to mitigate the risk of key compromise through side-channel attacks. Regular monitoring and vulnerability management practices, such as using tools like Vulert, can help maintain the security of your software.

See every vulnerability recorded for libgcrypt →

Share this vulnerability

FAQ

CVE-2018-0495 is a vulnerability in libgcrypt that allows a memory-cache side-channel attack on ECDSA signatures, potentially compromising cryptographic keys.

libgcrypt versions prior to 1.7.10 and 1.8.x before 1.8.3 are affected by this vulnerability.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score of CVE-2018-0495 is 4.7, indicating a moderate severity level.

If immediate updates are not possible, consider implementing additional security measures or using alternative libraries until the update can be applied.

Related vulnerabilities

Recent vulnerabilities recorded for libgcrypt.

How To Fix

Minimum fixed version

1.8.3-r0

This is the first release that contains the fix.

sudo apk add --upgrade libgcrypt

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