What is CVE-2023-50387?A high-severity flaw in Windows Server 2012, explained.
CVE-2023-50387 is a high-severity flaw (CVSS 7.5) in Windows Server 2012 from Microsoft, published on 14 February 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 over 99%. If you run an affected version, plan in the vendor’s fix.
Published 14 February 2024. Record last updated 17 June 2026. We keep this page's data up to date.
What is CVE-2023-50387? 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.
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
What kind of flaw is it?
- CWE-770Allocation of Resources Without Limits or Throttling
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
Is CVE-2023-50387 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 over 99%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Exploit likelihood jumped
- Exploit likelihood fell
- Record last updated
CVE-2023-50387 scores 71. Action: Patch now.
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-2023-50387 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-2023-50387? 13 products.
The published record lists 13 products from 8 vendors. Versions are shown as published: "4.8.0 to before 4.8.6" means from 4.8.0 up to, but not including, 4.8.6. If you run one of these, check your version, then go to the fix below.
- Operating system
Windows Server 2012
by Microsoft
Affected versionsr2 - Operating system
Enterprise Linux
by Red Hat
Affected versions6.07.08.09.0 - Application
Bind
by Isc
Affected versions9.0.0 to 9.16.469.18.0 to 9.18.229.19.0 to 9.19.20 - Application
Recursor
by Powerdns
Affected versions4.8.0 to before 4.8.64.9.0 to before 4.9.35.0.0 to before 5.0.2 - Application
Dnsmasq
by Thekelleys
Affected versionsbefore 2.90 - Operating system
Fedora
Affected versions39 - Application
Knot Resolver
by Nic
Affected versionsbefore 5.71 - Application
Unbound
by Nlnetlabs
Affected versionsbefore 1.19.1 - Operating system
Windows Server 2008
by Microsoft
Affected versionsr2-sp1
How do I fix CVE-2023-50387? 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
32 links- Releases (opens in a new tab)nic.cz
- Advisory for CVE-2023-50387 (opens in a new tab)microsoft.com
- Dnssec Vulnerability Internet (opens in a new tab)theregister.com · 2024
- Unbound 1.19.1 Released (opens in a new tab)nlnetlabs.nl · 2024
- oss-security mailing list post, 16 Feb 2024 (opens in a new tab)openwall.com · 2024
- oss-security mailing list post, 16 Feb 2024 (opens in a new tab)openwall.com · 2024
Does CVE-2023-50387 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
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consump...
- Matched to
- Windows Server 2012 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-2023-50387 is a high-severity flaw in Windows Server 2012 from Microsoft, published on 14 February 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-2023-50387 is 71 out of 100, which is High. Its action is "Patch now". 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 over 99%. That can change at any time, which is why we keep watching.
For Windows Server 2012 from Microsoft: r2. The record lists 13 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.