CVE-2022-38090: Improper isolation of shared resources in some Intel(R) Processors when using Intel(R) Software Guard Extensions may allow a privileged user…
Noroxi assessment
Priority: Monitor (action score 17/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. No special conditions are required; it is repeatable.
- Fixed version: intel-ucode (Alpine:v3.14) 20230214-r0; intel-microcode (Debian:10) 3.20230214.1~deb10u1; intel-microcode (Debian:12) 3.20230214.1.
Low priority for now. Upgrade to intel-ucode (Alpine:v3.14) 20230214-r0; intel-microcode (Debian:10) 3.20230214.1~deb10u1; intel-microcode (Debian:12) 3.20230214.1 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
Improper isolation of shared resources in some Intel(R) Processors when using Intel(R) Software Guard Extensions may allow a privileged user to potentially enable information disclosure via local access.
- Published
- Feb 16, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-922
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.4
- CNA · intel
- 6.0
- 1.6 point gap
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
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.
Is your version affected? Check itNoroxi 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 | xeon gold 5315y firmware | cpe:2.3:o:intel:xeon_gold_5315y_firmware |
| intel | xeon gold 5315y | cpe:2.3:h:intel:xeon_gold_5315y |
| intel | xeon gold 5317 firmware | cpe:2.3:o:intel:xeon_gold_5317_firmware |
| intel | xeon gold 5317 | cpe:2.3:h:intel:xeon_gold_5317 |
| intel | xeon gold 5318n firmware | cpe:2.3:o:intel:xeon_gold_5318n_firmware |
| intel | xeon gold 5318n | cpe:2.3:h:intel:xeon_gold_5318n |
| intel | xeon gold 5318s firmware | cpe:2.3:o:intel:xeon_gold_5318s_firmware |
| intel | xeon gold 5318s | cpe:2.3:h:intel:xeon_gold_5318s |
| intel | xeon gold 5318y firmware | cpe:2.3:o:intel:xeon_gold_5318y_firmware |
| intel | xeon gold 5318y | cpe:2.3:h:intel:xeon_gold_5318y |
| intel | xeon gold 5320 firmware | cpe:2.3:o:intel:xeon_gold_5320_firmware |
| intel | xeon gold 5320 | cpe:2.3:h:intel:xeon_gold_5320 |
and 188 more
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 Intel(R) Processors with Intel(R) Software Guard Extensions (SGX)
- See referencesaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel celeron j1750 firmwareall versions
- intel celeron j1800 firmwareall versions
- intel celeron j1850 firmwareall versions
- intel celeron j1900 firmwareall versions
- intel celeron j3060 firmwareall versions
- intel celeron j3160 firmwareall versions
- intel celeron j3355 firmwareall versions
- intel celeron j3355e firmwareall versions
- intel celeron j3455 firmwareall versions
- intel celeron j3455e firmwareall versions
- intel celeron j4005 firmwareall versions
- intel celeron j4025 firmwareall versions
- intel celeron j4105 firmwareall versions
- intel celeron j4125 firmwareall versions
- intel celeron j6412 firmwareall versions
- intel celeron j6413 firmwareall versions
- intel celeron n2805 firmwareall versions
- intel celeron n2806 firmwareall versions
- intel celeron n2807 firmwareall versions
- intel celeron n2808 firmwareall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.14 | intel-ucode | before 20230214-r0 | 20230214-r0 |
| Debian:10 | intel-microcode | before 3.20230214.1~deb10u1 | 3.20230214.1~deb10u1 |
| Debian:12 | intel-microcode | before 3.20230214.1 | 3.20230214.1 |
| openSUSE:Leap Micro 5.3 | ucode-intel | before 20230214-150200.21.1 | 20230214-150200.21.1 |
| openSUSE:Tumbleweed | ucode-intel | before 20230214-1.1 | 20230214-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | ucode-intel | before 20230214-150100.3.217.1 | 20230214-150100.3.217.1 |
| SUSE:Linux Enterprise Micro 5.3 | ucode-intel | before 20230214-150200.21.1 | 20230214-150200.21.1 |
| SUSE:Linux Enterprise Server 12 SP5 | ucode-intel | before 20230214-3.49.1 | 20230214-3.49.1 |
| SUSE:OpenStack Cloud 9 | ucode-intel | before 20230214-13.104.1 | 20230214-13.104.1 |
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-33060Out-of-bounds write in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of…31Monitor
- CVE-2022-21216Insufficient granularity of access control in out-of-band management in some Intel(R) Atom and Intel Xeon Scalable Processors may allow a…27Monitor
- CVE-2022-41804Unauthorized error injection in Intel(R) SGX or Intel(R) TDX for some Intel(R) Xeon(R) Processors may allow a privileged user to…26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-30539Feb 16, 2023 · Use after free in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege…26Monitor
- ← EarlierCVE-2022-33196Feb 16, 2023 · Incorrect default permissions in some memory controller configurations for some Intel(R) Xeon(R) Processors when using Intel(R) Software…26Monitor
- ← EarlierCVE-2022-33972Feb 16, 2023 · Incorrect calculation in microcode keying mechanism for some 3rd Generation Intel(R) Xeon(R) Scalable Processors may allow a privileged…17Monitor
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 |
|---|---|---|
| alpine:intel-ucode | 20230214-r0 · Alpine:v3.14 | Package registry (OSV) |
| debian:intel-microcode | 3.20230214.1 · Debian:12 | Package registry (OSV) |
| opensuse:ucode-intel | 20230214-150200.21.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| suse:ucode-intel | 20230214-150100.3.217.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | Package registry (OSV) |
| suse:ucode-intel | 20230214-150200.21.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.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-922 · Insecure Storage of Sensitive InformationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.