Microsoft Security Response Center

**According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do?** The user would have to click a specially crafted button for the attacker to successfully exploit the vulnerability.

**What type of information could be disclosed by this vulnerability?** The type of information that could be disclosed if an attacker successfully exploited this vulnerability is secrets or privileged information belonging to the user of the affected application.

Dependency on vulnerable third-party component in Microsoft Graphics Component allows an unauthorized attacker to execute code locally.

External control of file name or path in Azure Compute Gallery allows an authorized attacker to elevate privileges over a network.

Improper verification of cryptographic signature in GitHub allows an unauthorized attacker to perform spoofing over an adjacent network.

Exposure of sensitive information to an unauthorized actor in Windows NTLM allows an unauthorized attacker to perform spoofing locally.

Ai command injection in Visual Studio allows an authorized attacker to disclose information over a network.

Improper authentication in Windows SMB Server allows an authorized attacker to perform tampering over a network.

**How could an attacker exploit this vulnerability?** To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. Additionally, an attacker could convince a local user to open a malicious file. The attacker would have to convince the user to click a link, typically by way of an enticement in an email or instant message, and then convince them to open the specially crafted file.

Improper validation of specified type of input in Windows Local Session Manager (LSM) allows an authorized attacker to deny service over a network.