Bleichenbacher Timing Attacks in python-cryptography 3.2

py3-cryptography Updated 02 Oct 2025

Summary

11/01/2021
N/A
Yes i
Medium
5.9

CVE-2020-25659: python-cryptography 3.2 is vulnerable to Bleichenbacher timing attacks in the RSA decryption API, via timed processing of valid PKCS#1 v1.5 ciphertext. Affects py3-cryptography across 2 version ranges.

< 3.2.1-r0 < c9e65222c91df8b6f61650a3460e30232962c1e0

Fixed in 3.2.1-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

python-cryptography is a library for secure communications and cryptography in Python. It provides various cryptographic algorithms and protocols. The vulnerability affects version 3.2 of the library. This version is vulnerable to Bleichenbacher timing attacks in the RSA decryption API. An attacker can exploit this vulnerability by performing timed processing of valid PKCS#1 v1.5 ciphertext. The vulnerability can lead to unauthorized access to sensitive information.

Vulnerability Detail

The vulnerability in python-cryptography 3.2 allows for Bleichenbacher timing attacks in the RSA decryption API. This attack takes advantage of timing differences in the decryption process to extract sensitive information. By carefully timing the processing of valid PKCS#1 v1.5 ciphertext, an attacker can gain unauthorized access to encrypted data. This can result in the exposure of confidential information and compromise the security of the system.

How To Fix

Minimum fixed version

3.2.1-r0

This is the first release that contains the fix.

sudo apk add --upgrade py3-cryptography

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

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of python-cryptography to mitigate the risk of exploitation.

Conclusion

The vulnerability in python-cryptography 3.2 exposes systems to Bleichenbacher timing attacks, which can result in unauthorized access to sensitive information. It is crucial to upgrade to the fixed version (3.2.1-r0 or later) to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for py3-cryptography →

Share this vulnerability

FAQ

python-cryptography is a library for secure communications and cryptography in Python. It provides various cryptographic algorithms and protocols.

A Bleichenbacher timing attack is a cryptographic attack that exploits timing differences in the decryption process to extract sensitive information.

An attacker can exploit this vulnerability by performing timed processing of valid PKCS#1 v1.5 ciphertext, allowing them to gain unauthorized access to encrypted data.

The vulnerability can lead to unauthorized access to sensitive information, compromising the confidentiality and integrity of the system.

Yes, upgrading to python-cryptography version 3.2.1-r0 or later fixes the vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for py3-cryptography.

How To Fix

Minimum fixed version

3.2.1-r0

This is the first release that contains the fix.

sudo apk add --upgrade py3-cryptography

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