What is CVE-2021-3449?A medium-severity flaw in OpenSSL, explained.
CVE-2021-3449 is a medium-severity flaw (CVSS 5.9) in OpenSSL, published on 25 March 2021. 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 64%. If you run an affected version, plan in the vendor’s fix.
Published 25 March 2021. Record last updated 21 June 2024. We keep this page's data up to date.
What is CVE-2021-3449? 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.
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).
What kind of flaw is it?
- CWE-476NULL Pointer Dereference
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 offHard: conditions must line up
- 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:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2021-3449 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 64%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
- Exploit likelihood fell
CVE-2021-3449 scores 49. 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-2021-3449 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2021-3449? 167 products.
The published record lists 167 products from 12 vendors. Versions are shown as published: "1.1.1 to before 1.1.1k" means from 1.1.1 up to, but not including, 1.1.1k. If you run one of these, check your version, then go to the fix below.
- Application
OpenSSL
by OpenSSL
Affected versions1.1.1 to before 1.1.1k - Application
Node.js
by Nodejs
Affected versions10.0.0 to 10.12.010.13.0 to 10.24.012.0.0 to 12.12.012.13.0 to before 12.22.114.0.0 to 14.14.014.15.0 to before 14.16.1 - Application
Nessus Network Monitor
by Tenable
Affected versions5.11.05.11.15.12.05.12.15.13.0 - Application
Sinema Server
by Siemens
Affected versions14.014.0-sp114.0-sp214.0-sp2_update114.0-sp2_update2 - Application
Primavera Unifier
by Oracle
Affected versions17.7 to 17.1219.1220.1221.12 - Operating system
FreeBSD
by FreeBSD
Affected versions12.212.2-p112.2-p2 - Application
Graalvm
by Oracle
Affected versions19.3.520.3.1.221.0.0.2 - Application
Peoplesoft Enterprise Peopletools
by Oracle
Affected versions8.578.588.59 - Application
Web Gateway
by Mcafee
Affected versions8.2.199.2.1010.1.1
How do I fix CVE-2021-3449? Four steps.
- 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.
- 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.
- 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.
- 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
29 linksDoes CVE-2021-3449 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits t...
- Matched to
- OpenSSL on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2021-3449 is a medium-severity flaw in OpenSSL, published on 25 March 2021. 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 5.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2021-3449 is 49 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 64%. That can change at any time, which is why we keep watching.
For OpenSSL: 1.1.1 to before 1.1.1k. The record lists 167 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.