Cloudanix VulnDB

CVE-2014-5270

None

CVSS

—

EPSS

0.5%

Published

Oct 10, 2014

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A flaw in an encryption library lets someone standing next to a computer steal secret keys by measuring tiny electrical changes on the machine's metal parts.

Exploitation
Physical Access
Attacker needs
Physical Access
Complexity
Low
Impact
Data Exposure
Component
Library
Class
Information Disclosure
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Insufficient ciphertext normalization and randomization in Libgcrypt enables extraction of private keys through power-analysis side-channel attacks that measure voltage fluctuations on exposed hardware.

Why it matters to the business

Attackers with brief physical access to systems can recover encryption keys, exposing all data protected by affected cryptographic operations and undermining confidentiality of sensitive material.

How an attack unfolds

An attacker with physical proximity attaches voltage probes to exposed metal contacts on the device, captures power traces during cryptographic operations, and leverages the missing normalization and randomization to recover private keys without needing software access or network connectivity.

How to fix it

Upgrade Libgcrypt to version 1.5.4 or later and rebuild all dependent packages such as GnuPG; apply vendor patches for affected distributions.

How to confirm the fix worked

Confirm installed Libgcrypt version is 1.5.4 or newer via package manager queries and verify that cryptographic operations produce randomized ciphertext outputs under test conditions.

Typical attack path

  1. Obtain brief physical access to the target hardware
  2. Attach measurement equipment to exposed conductive surfaces
  3. Trigger cryptographic operations that use the vulnerable library
  4. Collect and analyze voltage traces to extract key material

How to detect it

No software-based indicators exist; physical access logs, tamper-evident seals, and hardware monitoring for unexpected probe attachments provide the only practical detection avenues.

What your security team should do

  • Prioritize upgrade of Libgcrypt on all systems handling cryptographic keys
  • Restrict physical access to hardware performing sensitive cryptographic operations
  • Audit dependencies to identify any remaining pre-1.5.4 instances

The record

Libgcrypt before 1.5.4, as used in GnuPG and other products, does not properly perform ciphertext normalization and ciphertext randomization, which makes it easier for physically proximate attackers to conduct key-extraction attacks by leveraging the ability to collect voltage data from exposed metal, a different vector than CVE-2013-4576.

Affected packages

Ecosystem Package Introduced Fixed
Debian:11 libgcrypt20 0 1.6.0-2
Debian:12 libgcrypt20 0 1.6.0-2
Debian:13 libgcrypt20 0 1.6.0-2
Debian:14 libgcrypt20 0 1.6.0-2
Debian:6.0 gnupg 0 1.4.10-4+squeeze6
Debian:6.0 libgcrypt11 0 1.4.5-2+squeeze2
Debian:7 gnupg 0 1.4.12-7+deb7u6
Debian:7 libgcrypt11 0 1.5.0-5+deb7u2
Mageia:3 gnupg 0 1.4.14-1.4.mga3
Mageia:3 libgcrypt 0 1.5.4-1.mga3
Mageia:4 libgcrypt 0 1.5.4-1.mga4
Ubuntu:14.04:LTS gnupg 0 1.4.16-1ubuntu2.1
Ubuntu:14.04:LTS gnupg 0 1.4.16-1ubuntu2.3
Ubuntu:14.04:LTS gnupg2 0 2.0.22-3ubuntu1.3
Ubuntu:14.04:LTS libgcrypt11 0 1.5.3-2ubuntu4.1
Ubuntu:14.04:LTS libgcrypt20 0 1.6.1-2ubuntu1

Related vulnerabilities