Sign inStart freeBook a demo

What is CVE-2024-6119?A high-severity flaw in OpenSSL, explained.

High severity19 affected products
The short answer

CVE-2024-6119 is a high-severity flaw (CVSS 7.5) in OpenSSL, published on 3 September 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 67%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 3 September 2024. Record last updated 17 June 2026. We keep this page's data up to date.

What it does

What is CVE-2024-6119? In plain terms.

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.

The official description

Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.

Impact summary: Abnormal termination of an application can a cause a denial of service.

Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an `otherName` subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program.

Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

What kind of flaw is it?

  • CWE-843Access of Resource Using Incompatible Type ('Type Confusion')
CVSS 3.1 scoreHigh · 7.5

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAnywhere on the internet
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstNo login needed
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan take it offline

Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation

Is CVE-2024-6119 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 67%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days67%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Exploit likelihood jumped
  3. Record last updated
How Precursor Intelligence ranks it
55out of 100Medium

CVE-2024-6119 scores 55. Action: Plan remediation.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2024-6119 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2024-6119? 19 products.

The published record lists 19 products from 2 vendors. Versions are shown as published: "3.0.0 to before 3.0.15" means from 3.0.0 up to, but not including, 3.0.15. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2024-6119? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

11 links
Precursor Intelligence

Does CVE-2024-6119 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2024-6119 is a high-severity flaw in OpenSSL, published on 3 September 2024. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.

It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2024-6119 is 55 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 67%. That can change at any time, which is why we keep watching.

For OpenSSL: 3.0.0 to before 3.0.15, 3.1.0 to before 3.1.7, 3.2.0 to before 3.2.3, 3.3.0 to before 3.3.2. The record lists 19 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring