Windows DNS Spoofing Vulnerability
🔗 CVE IDs covered (1)
📋 Description
According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability? The attacker must inject themselves into the logical network path between the target and the resource requested by the victim to read or modify network communications. This is called a machine-in-the-middle (MITM) attack.
According to the CVSS metric, user interaction is required (UI:R) and privileges required are none (PR:N). What does that mean for this vulnerability? An unauthorized attacker must wait for a user to initiate a connection.
🎯 Affected products15
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
- Windows Server 2012
- Windows Server 2012 (Server Core installation)
- Windows Server 2012 R2
- Windows Server 2012 R2 (Server Core installation)
- Windows Server 2016
- Windows Server 2016 (Server Core installation)
- Windows Server 2019
- Windows Server 2019 (Server Core installation)
- Windows Server 2022
- Windows Server 2022 (Server Core installation)
- Windows Server 2022, 23H2 Edition (Server Core installation)
- Windows Server 2025
- Windows Server 2025 (Server Core installation)
✅ Remediation
KB5046615 (Security Update) — fixed build 10.0.17763.6532 KB5046616 (Security Update) — fixed build 10.0.20348.2849 KB5046698 (SecurityHotpatchUpdate) — fixed build 10.0.20348.2819 KB5046618 (Security Update) — fixed build 10.0.25398.1251 KB5046612 (Security Update) — fixed build 10.0.14393.7515 KB5046687 (Monthly Rollup) — fixed build 6.1.7601.27415 KB5046705 (Security Only) — fixed build 6.1.7601.27415 KB5046697 (Monthly Rollup) — fixed build 6.2.9200.25165 KB5046682 (Monthly Rollup) — fixed build 6.3.9600.22267 KB5046617 (Security Update) — fixed build 10.0.26100.2314 KB5046696 (SecurityHotpatchUpdate) — fixed build 10.0.26100.2240
🔗 References (23)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43450
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046615
- referencehttps://support.microsoft.com/help/5046615
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046616
- referencehttps://support.microsoft.com/help/5046616
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046698
- referencehttps://support.microsoft.com/help/5046698
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046618
- referencehttps://support.microsoft.com/help/5046618
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046612
- referencehttps://support.microsoft.com/help/5046612
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046687
- referencehttps://support.microsoft.com/help/5046687
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046705
- referencehttps://support.microsoft.com/help/5046705
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046697
- referencehttps://support.microsoft.com/help/5046697
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046682
- referencehttps://support.microsoft.com/help/5046682
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046617
- referencehttps://support.microsoft.com/help/5046617
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046696
- referencehttps://support.microsoft.com/help/5046696