CVE-2019-6486: Denial of Service in crypto/elliptic P-521 and P-384 curves

stdlib Updated 02 Oct 2025

Summary

24/05/2022
Yes i
Unrated
Not published

CVE-2019-6486: Denial of service affecting P-521 and P-384 curves in crypto/elliptic. Affects stdlib across 2 version ranges.

< 1.10.8 >= 1.11.0-0, < 1.11.5

Fixed in 1.10.8 or 1.11.5, depending on the release line you run. 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

The stdlib package in the Go ecosystem provides a collection of standard libraries for the Go programming language. One of the packages included is crypto/elliptic, which implements elliptic curve cryptography. This package offers support for various elliptic curves, including P-521 and P-384. Elliptic curve cryptography is widely used for secure communication protocols, digital signatures, and key exchange mechanisms.

Vulnerability Detail

A Denial of Service (DoS) vulnerability has been identified in the crypto/elliptic implementation of the P-521 and P-384 elliptic curves. This vulnerability allows an attacker to create inputs that consume excessive amounts of CPU resources. The attacker can exploit this vulnerability through various means, such as delivering the malicious inputs via TLS handshakes, X.509 certificates, JWT tokens, ECDH shares, or ECDSA signatures. If an ECDH private key is reused multiple times, the attack can also lead to key recovery. This vulnerability poses a significant risk to systems relying on the affected elliptic curves for cryptographic operations.

How To Fix

Latest published version: go1.25.5 as of 22 Oct 2026

go get stdlib@vgo1.25.5

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.10.8 1.10.8
    go get stdlib@v1.10.8
  • >= 1.11.0-0, < 1.11.5 1.11.5
    go get stdlib@v1.11.5

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to apply the recommended fix by updating the Go stdlib package to the patched versions.

Conclusion

The Denial of Service vulnerability in the P-521 and P-384 elliptic curves of the crypto/elliptic implementation in the Go stdlib package poses a significant risk to systems relying on these curves for cryptographic operations. It is crucial to update the Go stdlib package to the patched versions to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for stdlib →

Share this vulnerability

FAQ

This vulnerability allows an attacker to launch a DoS attack, causing excessive CPU consumption. In some cases, it can also lead to key recovery if an ECDH private key is reused.

The vulnerability can be exploited by crafting malicious inputs and delivering them through various channels, such as TLS handshakes, X.509 certificates, JWT tokens, ECDH shares, or ECDSA signatures.

Versions prior to 1.10.8 and 1.11.5 of the Go stdlib package are affected by this vulnerability.

No, there are no known workarounds for this vulnerability. Updating to the patched versions of the Go stdlib package is the recommended solution.

Key recovery is only possible if an ECDH private key is reused multiple times. It is important to avoid reusing ECDH private keys to mitigate this risk.

Related vulnerabilities

Recent vulnerabilities recorded for stdlib.

How To Fix

Latest published version: go1.25.5 as of 22 Oct 2026

go get stdlib@vgo1.25.5

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.10.8 1.10.8
    go get stdlib@v1.10.8
  • >= 1.11.0-0, < 1.11.5 1.11.5
    go get stdlib@v1.11.5

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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