| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Intel Xeon. This vulnerability affects unknown code of the component SGX. This manipulation causes custom special character. The identification of this vulnerability is CVE-2024-23918. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability classified as critical was found in Intel Xeon (affected version not known). Affected by this vulnerability is some unknown functionality of the component SGX. The manipulation with an unknown input leads to a custom special character vulnerability. The CWE definition for the vulnerability is CWE-92. This entry has been deprecated. It originally came from PLOVER, which sometimes defined "other" and "miscellaneous" categories in order to satisfy exhaustiveness requirements for taxonomies. Within the context of CWE, the use of a more abstract entry is preferred in mapping situations. CWE-75 is a more appropriate mapping. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Improper conditions check in some Intel(R) Xeon(R) processor memory controller configurations when using Intel(R) SGX may allow a privileged user to potentially enable escalation of privilege via local access.
It is possible to read the advisory at intel.com. This vulnerability is known as CVE-2024-23918 since 02/08/2024. The exploitation appears to be easy. 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 11/16/2024).
The vulnerability scanner Nessus provides a plugin with the ID 211478 (Fedora 41 : microcode_ctl (2024-28ea86c8aa)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (211478). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.intel.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (intel): 🔍
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: Custom special characterCWE: CWE-92 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: 211478
Nessus Name: Fedora 41 : microcode_ctl (2024-28ea86c8aa)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/08/2024 🔍11/13/2024 🔍
11/13/2024 🔍
11/16/2024 🔍
Sources
Vendor: intel.comAdvisory: intel-sa-01079
Status: Not defined
CVE: CVE-2024-23918 (🔍)
GCVE (CVE): GCVE-0-2024-23918
GCVE (VulDB): GCVE-100-284419
Entry
Created: 11/13/2024 22:32Updated: 11/16/2024 09:47
Changes: 11/13/2024 22:32 (74), 11/16/2024 09:47 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Issues in the memory controller configurations of Intel Xeon processors may also involve microcode updates to address these vulnerabilities.
Given this, I kindly request that the CPE intel:microcode be considered in relation to this vulnerability.
Want to know what is going to be exploited?
We predict KEV entries!