Microsoft Windows Server 2022 23H2 Update Stack sensitive data storage in improperly locked memory
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Microsoft Windows Server 2022 23H2. It has been rated as critical. This affects an unknown part of the component Update Stack. This manipulation causes sensitive data storage in improperly locked memory. This vulnerability is tracked as CVE-2024-26236. The attack is restricted to local execution. No exploit exists. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability has been found in Microsoft Windows Server 2022 23H2 and classified as critical. Affected by this vulnerability is an unknown function of the component Update Stack. The manipulation with an unknown input leads to a sensitive data storage in improperly locked memory vulnerability. The CWE definition for the vulnerability is CWE-591. The product stores sensitive data in memory that is not locked, or that has been incorrectly locked, which might cause the memory to be written to swap files on disk by the virtual memory manager. This can make the data more accessible to external actors. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 04/09/2024 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. This vulnerability is known as CVE-2024-26236. The exploitation appears to be difficult. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 04/09/2024).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.0
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.0
Vendor Vector (Microsoft): 🔍
CNA Base Score: 7.0
CNA Vector (Microsoft): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Sensitive data storage in improperly locked memoryCWE: CWE-591 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
02/15/2024 🔍04/09/2024 🔍
04/09/2024 🔍
04/09/2024 🔍
05/14/2024 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2024-26236 (🔍)
GCVE (CVE): GCVE-0-2024-26236
GCVE (VulDB): GCVE-100-259987
Entry
Created: 04/09/2024 19:47Updated: 05/14/2024 23:13
Changes: 04/09/2024 19:47 (32), 04/09/2024 19:48 (2), 04/09/2024 19:51 (35), 05/14/2024 23:01 (1), 05/14/2024 23:13 (10)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.