Microsoft Windows up to Server 2022 23H2 Mobile Broadband Driver redirect
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Microsoft Windows up to Server 2022 23H2 and classified as critical. Affected by this issue is some unknown functionality of the component Mobile Broadband Driver. This manipulation causes redirect. The identification of this vulnerability is CVE-2024-43536. It is feasible to perform the attack on the physical device. There is no exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Microsoft Windows up to Server 2022 23H2. It has been declared as critical. Affected by this vulnerability is an unknown part of the component Mobile Broadband Driver. The manipulation with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Windows Mobile Broadband Driver Remote Code Execution Vulnerability
The weakness was shared 10/08/2024 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. This vulnerability is known as CVE-2024-43536. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/17/2024). MITRE ATT&CK project uses the attack technique T1204.001 for this issue.
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 the best quality for vulnerability data then you always have to consider 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: 6.8VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.8
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 6.8
Vendor Vector (Microsoft): 🔍
CNA Base Score: 6.8
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: RedirectCWE: CWE-601
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
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
10/08/2024 🔍10/08/2024 🔍
10/08/2024 🔍
10/17/2024 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2024-43536 (🔍)
GCVE (CVE): GCVE-0-2024-43536
GCVE (VulDB): GCVE-100-279709
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 10/08/2024 20:13Updated: 10/17/2024 10:28
Changes: 10/08/2024 20:13 (35), 10/08/2024 20:16 (34), 10/17/2024 10:28 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.