CVE-2024-43450
Improper Enforcement of Message Integrity During Transmission in a Communication Channel (CWE-924)
Summary
Windows DNS Spoofing Vulnerability. This vulnerability has a high impact on integrity, availability, and confidentiality. It requires user interaction and can be exploited over a network, although the attack complexity is high. No privileges are required to exploit this vulnerability.
Impact
This vulnerability could allow an attacker to perform DNS spoofing attacks, potentially redirecting network traffic to malicious sites. The high impact on integrity, confidentiality, and availability suggests that successful exploitation could lead to unauthorized data modification, information disclosure, and service disruptions. Given the need for user interaction, attacks might involve social engineering tactics to trick users into taking specific actions that trigger the vulnerability.
Exploitation
There is no evidence that a public proof-of-concept exists. There is no evidence of proof of exploitation at the moment.
Patch
A patch is available. Microsoft released a security update on November 12, 2024, to address this vulnerability.
Mitigation
1. Apply the security update provided by Microsoft as soon as possible. 2. Implement network segmentation and access controls to limit potential attack vectors. 3. Educate users about the risks of interacting with suspicious network requests or links. 4. Monitor DNS traffic for unusual patterns that might indicate spoofing attempts. 5. Consider implementing DNSSEC (Domain Name System Security Extensions) to add an extra layer of authentication to DNS queries and responses.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Timeline
Detection for the vulnerability has been added to Qualys (92186)
A CVSS base score of 7.5 has been assigned.
Feedly found the first article mentioning CVE-2024-43450. See article
Feedly estimated the CVSS score as HIGH
Feedly estimated the CVSS score as MEDIUM
NVD published the first details for CVE-2024-43450
EPSS Score was set to: 0.09% (Percentile: 40.2%)
This CVE started to trend in security discussions
This CVE stopped trending in security discussions