Microsoft Windows up to Server 2022 Point-to-Point Tunneling Protocol race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Microsoft Windows. This issue affects some unknown processing of the component Point-to-Point Tunneling Protocol. The manipulation leads to an unknown weakness. This vulnerability is listed as CVE-2022-38000. The attack may be initiated remotely. There is no available exploit. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Microsoft Windows (Operating System) and classified as critical. This issue affects an unknown functionality of the component Point-to-Point Tunneling Protocol. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. Impacted is confidentiality, integrity, and availability.
The weakness was presented 10/11/2022 as confirmed security guidance (Website). The advisory is shared at portal.msrc.microsoft.com. The identification of this vulnerability is CVE-2022-38000. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/21/2026).
It is declared as proof-of-concept.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-40607). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 7 SP1
- 8.1
- 10
- 10 20H2
- 10 21H1
- 10 21H2
- 10 1607
- 10 1809
- 11
- 11 22H2
- RT 8.1
- Server 2008 R2 SP1
- Server 2012
- Server 2012 R2
- Server 2016
- Server 2019
- Server 2022
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.1VulDB Meta Temp Score: 7.3
VulDB Base Score: 8.1
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 8.1
Vendor 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: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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
08/08/2022 🔍10/11/2022 🔍
10/11/2022 🔍
10/11/2022 🔍
06/21/2026 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: portal.msrc.microsoft.com
Status: Confirmed
CVE: CVE-2022-38000 (🔍)
GCVE (CVE): GCVE-0-2022-38000
GCVE (VulDB): GCVE-100-210533
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 10/11/2022 20:56Updated: 06/21/2026 06:13
Changes: 10/11/2022 20:56 (14), 10/11/2022 20:57 (21), 10/11/2022 21:00 (19), 11/06/2022 08:09 (2), 11/06/2022 08:10 (2), 06/21/2026 06:13 (15)
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.