Microsoft Windows up to Server 2022 AMD CPU Branch type confusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Microsoft Windows. The impacted element is an unknown function of the component AMD CPU Branch. This manipulation causes type confusion. This vulnerability appears as CVE-2022-23825. There is no available exploit. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability has been found in Microsoft Windows (Operating System) and classified as problematic. Affected by this vulnerability is an unknown code of the component AMD CPU Branch. The manipulation with an unknown input leads to a type confusion vulnerability. The CWE definition for the vulnerability is CWE-843. The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was presented 07/12/2022 as confirmed security guidance (Website). It is possible to read the advisory at portal.msrc.microsoft.com. This vulnerability is known as CVE-2022-23825. 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 10/15/2024).
The vulnerability scanner Nessus provides a plugin with the ID 208564 (CentOS 7 : kernel (RHSA-2022:7337)), which helps to determine the existence of the flaw in a target environment.
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 Tenable (208564). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 7 SP1
- 8.1
- 10
- 10 20H2
- 10 21H1
- 10 21H2
- 10 1607
- 10 1809
- 11
- RT 8.1
- Server 2008 R2 SP1
- Server 2008 SP2
- 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: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Type confusionCWE: CWE-843
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 208564
Nessus Name: CentOS 7 : kernel (RHSA-2022:7337)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
01/21/2022 🔍07/12/2022 🔍
07/12/2022 🔍
07/12/2022 🔍
10/15/2024 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: FEDORA-2022-3e6ce58029
Status: Confirmed
CVE: CVE-2022-23825 (🔍)
GCVE (CVE): GCVE-0-2022-23825
GCVE (VulDB): GCVE-100-203683
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 07/12/2022 22:04Updated: 10/15/2024 18:53
Changes: 07/12/2022 22:04 (13), 07/12/2022 22:08 (30), 07/22/2022 14:28 (3), 10/15/2024 18:53 (16)
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.