CVE-2018-0734

What it is

The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

12.2% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-10-30 12:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-08 22:16 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 12.2% in the next 30 days (EPSS).
• Severity: 5.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-10-30 12:29 UTC

Last modified

2026-10-08 22:16 UTC

Exploit probability

12.2% · EPSS, next 30 days

Weakness

CWE-327 · Broken cryptographic algorithm

Record status

Modified

Affected

• OpenSSL ≤ 1.0.2p
• OpenSSL ≤ 1.1.0i
• OpenSSL 1.1.1
• Canonical Ubuntu Linux 14.04
• Canonical Ubuntu Linux 16.04
• Canonical Ubuntu Linux 18.04
• Canonical Ubuntu Linux 18.10
• Debian Linux 9.0

Attack profile CVSS 3.1 · 5.9

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2018-0734.md and follow it. Check whether this project is affected by CVE-2018-0734. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge