Microsoft Windows up to Server 2022 23H2 Secure Boot heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $5k-$25k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Microsoft Windows 11 21H2/11 22H2/11 23H2/Server 2022/Server 2022 23H2. Affected by this issue is some unknown functionality of the component Secure Boot. The manipulation results in heap-based overflow. This vulnerability is known as CVE-2024-37977. Access to the local network is required for this attack. No exploit is available. A patch should be applied to remediate this issue.
Details
A vulnerability classified as critical has been found in Microsoft Windows 11 21H2/11 22H2/11 23H2/Server 2022/Server 2022 23H2. Affected is an unknown functionality of the component Secure Boot. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 07/09/2024 as confirmed security update guide (Website). The advisory is available at msrc.microsoft.com. This vulnerability is traded as CVE-2024-37977. The exploitability is told to be easy. The attack can only be done within the local network. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 07/10/2024).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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: 8.0VulDB Meta Temp Score: 7.3
VulDB Base Score: 8.0
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 8.0
Vendor Vector (Microsoft): 🔍
CNA Base Score: 8.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: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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
07/09/2024 🔍07/09/2024 🔍
07/09/2024 🔍
03/20/2025 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2024-37977 (🔍)
GCVE (CVE): GCVE-0-2024-37977
GCVE (VulDB): GCVE-100-270810
Entry
Created: 07/09/2024 20:00Updated: 03/20/2025 01:06
Changes: 07/09/2024 20:00 (35), 07/09/2024 20:03 (34), 07/10/2024 08:59 (10), 03/20/2025 01:06 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.