# CVE-2019-13627: Weak cryptography in n/a > An attacker can exploit a timing side-channel in libgcrypt's ECDSA implementation to potentially recover private keys. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 25 Sep 2019 - **Updated:** 14 Oct 2026 - **Also known as:** ALPINE-CVE-2019-13627, AZL-41066, DEBIAN-CVE-2019-13627, DLA-1931-1, DLA-1931-2, GHSA-vwvj-6vw9-cw8w, MGASA-2019-0256, RHSA-2020:4482, RLSA-2020:4482, SUSE-SU-2019:2349-1, SUSE-SU-2019:2510-1, SUSE-SU-2019:3392-1, UBUNTU-CVE-2019-13627, USN-4236-1, USN-4236-2, USN-4236-3, openSUSE-SU-2019:2161-1, openSUSE-SU-2020:0022-1 ## What is CVE-2019-13627? CVE-2019-13627 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 25 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7. Weakness: CWE-203 (Observable Discrepancy) ## Which versions are affected by CVE-2019-13627? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libgcrypt` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-4.el8 | | `libgcrypt-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-4.el8 | | `libgcrypt-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-4.el8 | | `libgcrypt-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-4.el8 | | `libgcrypt-devel-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-4.el8 | | `libgcrypt` | Rocky Linux:8 | All versions | 0:1.8.5-4.el8 | | `libgcrypt` | SUSE:Enterprise Storage 4 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Enterprise Storage 5 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:HPE Helion OpenStack 8 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 1.8.2-6.20.1 | | `libgcrypt` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 1.8.2-8.12.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:OpenStack Cloud 7 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:OpenStack Cloud 8 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 1.6.1-16.68.1 | | `libgcrypt` | openSUSE:Leap 15.0 | All versions | 1.8.2-lp150.5.13.1 | | `libgcrypt` | openSUSE:Leap 15.1 | All versions | 1.8.2-lp151.9.7.1 | Products: Canonical Ubuntu Linux, Libgcrypt20 Project Libgcrypt20, Opensuse Leap. ## How do I fix CVE-2019-13627? Upgrade to a fixed version. ## Is CVE-2019-13627 being exploited? There is no known exploitation of CVE-2019-13627 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-13627 and fix it if it is affected. What it is: CVE-2019-13627 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 25 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-13627 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-13627/ (Markdown: https://insights.sbomify.com/CVE-2019-13627/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13627 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13627 - OSV: https://osv.dev/vulnerability/CVE-2019-13627 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-13627/ Summaries are generated and may contain mistakes; the official description above is the record.