CVE-2023-22655: Protection mechanism failure in some 3rd and 4th Generation Intel(R) Xeon(R) Processors when using Intel(R) SGX or Intel(R) TDX may allow a
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: microcode_ctl (AlmaLinux:9) 4:20240910-1.el9_5; intel-ucode (Alpine:v3.17) 20240813-r0; intel-ucode (Alpine:v3.19) 20240312-r0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to microcode_ctl (AlmaLinux:9) 4:20240910-1.el9_5; intel-ucode (Alpine:v3.17) 20240813-r0; intel-ucode (Alpine:v3.19) 20240312-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Protection mechanism failure in some 3rd and 4th Generation Intel(R) Xeon(R) Processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
- Published
- Mar 14, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-693
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · intel
- 6.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| intel | 3rd gen intel xeon scalable processor family | cpe:2.3:a:intel:3rd_gen_intel_xeon_scalable_processor_family |
| intel | xeon d processor | cpe:2.3:h:intel:xeon_d_processor |
| intel | 4th generation intel xeon platinum processors | cpe:2.3:h:intel:4th_generation_intel_xeon_platinum_processors |
| intel | 4th generation intel xeon gold processors | cpe:2.3:h:intel:4th_generation_intel_xeon_gold_processors |
| intel | 4th gen intel xeon scalable processors | cpe:2.3:h:intel:4th_gen_intel_xeon_scalable_processors |
| intel | 4th gen intel xeon platinum processors | cpe:2.3:h:intel:4th_gen_intel_xeon_platinum_processors |
| intel | 4th gen intel xeon gold processors | cpe:2.3:h:intel:4th_gen_intel_xeon_gold_processors |
| intel | 4th gen intel xeon silver processors | cpe:2.3:h:intel:4th_gen_intel_xeon_silver_processors |
| intel | 4th gen intel xeon bronze processors | cpe:2.3:h:intel:4th_gen_intel_xeon_bronze_processors |
| intel | xeon cpu max series processors | cpe:2.3:h:intel:xeon_cpu_max_series_processors |
| intel | 4th gen intel xeon scalable processors with intel vran | cpe:2.3:h:intel:4th_gen_intel_xeon_scalable_processors_with_intel_vran |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.
n/a 3rd and 4th Generation Intel(R) Xeon(R) Processors when using Intel(R) SGX or Intel(R) TDX
- See referencesaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | microcode_ctl | before 4:20240910-1.el9_5 | 4:20240910-1.el9_5 |
| Alpine:v3.17 | intel-ucode | before 20240813-r0 | 20240813-r0 |
| Alpine:v3.19 | intel-ucode | before 20240312-r0 | 20240312-r0 |
| Debian:10 | intel-microcode | before 3.20240312.1~deb10u1 | 3.20240312.1~deb10u1 |
| Debian:12 | intel-microcode | before 3.20240312.1~deb12u1 | 3.20240312.1~deb12u1 |
| Debian:13 | intel-microcode | before 3.20240312.1 | 3.20240312.1 |
| openSUSE:Leap Micro 5.3 | ucode-intel | before 20240312-150200.38.1 | 20240312-150200.38.1 |
| openSUSE:Tumbleweed | ucode-intel | before 20240312-1.1 | 20240312-1.1 |
| Red Hat:enterprise_linux:9::baseos | microcode_ctl | before 4:20230808-2.20240531.1.el9_4 | 4:20230808-2.20240531.1.el9_4 |
| Red Hat:enterprise_linux:9::baseos | microcode_ctl | before 4:20240910-1.el9_5 | 4:20240910-1.el9_5 |
| Rocky Linux:9 | microcode_ctl | before 4:20240910-1.el9_5 | 4:20240910-1.el9_5 |
| SUSE:Linux Enterprise Micro 5.3 | ucode-intel | before 20240312-150200.38.1 | 20240312-150200.38.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | microcode_ctl | before 1.17-102.83.81.1 | 1.17-102.83.81.1 |
| SUSE:Linux Enterprise Server 12 SP5 | ucode-intel | before 20240312-134.1 | 20240312-134.1 |
| SUSE:Linux Micro 6.0 | ucode-intel | before 20240813-1.1 | 20240813-1.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:microcode_ctl | 4:20240910-1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| alpine:intel-ucode | 20240813-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:intel-microcode | 3.20240312.1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:ucode-intel | 20240312-150200.38.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| red hat:microcode_ctl | 4:20230808-2.20240531.1.el9_4 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| rocky linux:microcode_ctl | 4:20240910-1.el9_5 · Rocky Linux:9 | Package registry (OSV) |
| suse:microcode_ctl | 1.17-102.83.81.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:ucode-intel | 20240312-134.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:ucode-intel | 20240312-150200.38.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0211 · Mar 20, 2024(Intel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-693 · Protection Mechanism FailureCVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Site TracingCAPEC-107likelihood: Medium · Very High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Escaping a Sandbox by Calling Code in Another LanguageCAPEC-237likelihood: Low · Very High
- Using Unpublished Interfaces or FunctionalityCAPEC-36likelihood: Medium · High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.