Critical Vulnerability in OpenSSL: Key Recovery Risk Due to Co-factor Absence

openssl Updated 02 Oct 2025

Summary

10/09/2019
N/A
Yes i
Medium
4.7

ALPINE-CVE-2019-1547: Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. Affects openssl versions < 1.1.1d-r0. Fixed in 1.1.1d-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

OpenSSL is a widely-used open-source software library that provides robust cryptographic functions, including secure communication over networks. It is integral to various applications, ensuring data integrity and confidentiality. However, certain versions of OpenSSL are vulnerable to a significant security flaw that can lead to key recovery during ECDSA signature operations, particularly when explicit parameters without a co-factor are used.

Vulnerability Detail

The vulnerability, identified as CVE-2019-1547, arises from the ability to construct EC groups using explicit parameters that may lack a co-factor. This absence can lead OpenSSL to revert to non-side channel resistant code paths, exposing the system to potential key recovery attacks during ECDSA signature operations. An attacker would need to time the creation of numerous signatures using these vulnerable parameters, which could result in the compromise of cryptographic keys. This issue affects versions 1.1.1-1.1.1c and earlier, as well as 1.1.0-1.1.0k and 1.0.2-1.0.2s.

How To Fix

Minimum fixed version

1.1.1d-r0

This is the first release that contains the fix.

sudo apk add --upgrade openssl

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

Workaround

As a workaround, avoid using explicit parameters for EC groups in your applications. Ensure that your implementation relies on named curves, which are not affected by this vulnerability.

Conclusion

The CVE-2019-1547 vulnerability in OpenSSL poses a significant risk of key recovery during ECDSA signature operations due to the absence of a co-factor in certain EC groups. It is crucial to update to the latest patched versions of OpenSSL to safeguard against potential attacks. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for openssl →

Share this vulnerability

FAQ

CVE-2019-1547 is a vulnerability in OpenSSL that can lead to key recovery during ECDSA signature operations due to the absence of a co-factor in certain EC groups.

Affected versions include OpenSSL 1.1.1-1.1.1c, 1.1.0-1.1.0k, and 1.0.2-1.0.2s.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

The CVSS score for CVE-2019-1547 is 4.7, indicating a moderate severity level.

If immediate updates are not possible, ensure that your application does not use explicit parameters for EC groups and relies on named curves to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for openssl.

How To Fix

Minimum fixed version

1.1.1d-r0

This is the first release that contains the fix.

sudo apk add --upgrade openssl

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