Exposed dangerous method or function in Windows Local Session Manager (LSM) allows an authorized attacker to deny service over a network.
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Windows_11_22h2 | Microsoft | * | 10.0.22621.5189 (excluding) |
| Windows_11_23h2 | Microsoft | * | 10.0.22631.5189 (excluding) |
| Windows_11_24h2 | Microsoft | * | 10.0.26100.3775 (excluding) |
| Windows_server_2022 | Microsoft | * | 10.0.20348.3453 (excluding) |
| Windows_server_2022_23h2 | Microsoft | * | 10.0.25398.1551 (excluding) |
| Windows_server_2025 | Microsoft | * | 10.0.26100.3775 (excluding) |
This weakness can lead to a wide variety of resultant weaknesses, depending on the behavior of the exposed method. It can apply to any number of technologies and approaches, such as ActiveX controls, Java functions, IOCTLs, and so on. The exposure can occur in a few different ways:
Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be:
Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.