Loading vulnerability…
Windows COM Server Information Disclosure Vulnerability
A type confusion vulnerability in Windows COM can allow an authorized local attacker to access a resource using an incompatible type and disclose sensitive information. The flaw affects Windows COM server functionality and is classified as an information disclosure issue rather than a code execution or integrity-impacting bug. Microsoft indicates that successful exploitation could allow reading of user mode service memory.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a local authenticated attacker to disclose sensitive information from memory, including potentially reading user mode service memory. The vulnerability has high confidentiality impact, with no indicated impact on integrity or availability.
If you can’t patch tonight, do this now.
No specific workaround or mitigation beyond applying the vendor-provided security update is currently available from the provided information. Standard hardening measures that restrict local logon and execution by untrusted users may reduce exposure until patching is completed.
Patch, then assume compromise.
Apply the official Microsoft security update for the affected Windows products. Prioritize patching systems where local low-privilege users can log on or execute code, as the vulnerability requires local access and low privileges.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.