Critical Timing Side Channel Vulnerability in libcrypto++ Package

libcrypto++ Updated 02 Oct 2025

Summary

22/08/2023
N/A
No i
High
7.5

UBUNTU-CVE-2022-48570: Crypto++ through 8.4 contains a timing side channel in ECDSA signature generation. Affects libcrypto++ versions 5.6.1-6 – 5.6.1-6+deb8u3ubuntu0.1~esm1. No fix is published. 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

libcrypto++ is a widely used C++ library that provides a rich set of cryptographic algorithms and protocols. It is essential for developers needing secure encryption, decryption, and hashing functionalities in their applications. However, the library has been found to have a significant vulnerability that can compromise the security of applications relying on it.

Vulnerability Detail

Crypto++ through version 8.4 contains a timing side channel vulnerability in ECDSA signature generation. The issue arises from the FixedSizeAllocatorWithCleanup function, which could write to memory outside of the allocated space if the memory was not aligned to a 16-byte boundary. This vulnerability exists because the fix for CVE-2019-14318 was intentionally removed to maintain certain functionalities, leading to potential security risks such as unauthorized access to sensitive data or manipulation of cryptographic operations.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, developers can avoid using the affected ECDSA signature generation functions until the package is updated. Additionally, ensuring proper memory alignment in custom implementations may mitigate some risks.

Conclusion

The libcrypto++ package has a critical vulnerability that can lead to severe security risks. It is essential for users to update to the latest version to mitigate these risks. Understanding the nature of the vulnerability and implementing the recommended fixes will help maintain the integrity and security of applications utilizing this library.

See every vulnerability recorded for libcrypto++ →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 7.5, indicating a high severity level.

Versions of libcrypto++ up to 8.4 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 vulnerability could lead to unauthorized access to sensitive data or manipulation of cryptographic operations, compromising the security of applications.

Yes, updating to the latest patched version of the libcrypto++ package is the recommended permanent fix.

Related vulnerabilities

Recent vulnerabilities recorded for libcrypto++.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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