Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclos
Noroxi assessment
Priority: Monitor (action score 22/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.51% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: intel-ucode (Alpine:v3.13) 20201112-r0, 20210216-r0, 20201110-r0; intel-microcode (Debian:12) 3.20201110.1; intel-microcode (Debian:9) 3.20201118.1~deb9u1.
- Mentioned 4 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to intel-ucode (Alpine:v3.13) 20201112-r0, 20210216-r0, 20201110-r0; intel-microcode (Debian:12) 3.20201110.1; intel-microcode (Debian:9) 3.20201118.1~deb9u1 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 may allow an authenticated user to potentially enable information disclosure via local access.
- BDU:2020-05479
- DLA-2546-1
- openSUSE-SU-2020:2075-1
- openSUSE-SU-2020:2098-1
- openSUSE-SU-2024:11478-1
- RHSA-2020:5083
- RHSA-2020:5084
- RHSA-2020:5085
- RHSA-2020:5181
- RHSA-2020:5182
- RHSA-2020:5183
- RHSA-2020:5184
- RHSA-2020:5185
- RHSA-2020:5186
- RHSA-2020:5188
- RHSA-2020:5189
- RHSA-2020:5190
- RHSA-2020:5369
- RHSA-2021:3027
- RHSA-2021:3028
- Published
- Nov 12, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 42th percentile
- CWE
- CWE-668
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
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 | microcode | cpe:2.3:o:intel:microcode |
| intel | core i3-1000g1 | cpe:2.3:h:intel:core_i3-1000g1 |
| intel | core i3-1000g4 | cpe:2.3:h:intel:core_i3-1000g4 |
| intel | core i3-1005g1 | cpe:2.3:h:intel:core_i3-1005g1 |
| intel | core i3-1110g4 | cpe:2.3:h:intel:core_i3-1110g4 |
| intel | core i3-1115g4 | cpe:2.3:h:intel:core_i3-1115g4 |
| intel | core i3-1120g4 | cpe:2.3:h:intel:core_i3-1120g4 |
| intel | core i3-1125g4 | cpe:2.3:h:intel:core_i3-1125g4 |
| intel | core i5-1030g4 | cpe:2.3:h:intel:core_i5-1030g4 |
| intel | core i5-1030g7 | cpe:2.3:h:intel:core_i5-1030g7 |
| intel | core i5-1035g1 | cpe:2.3:h:intel:core_i5-1035g1 |
| intel | core i5-1035g4 | cpe:2.3:h:intel:core_i5-1035g4 |
and 37 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux9.0
- fedoraproject fedora31
- intel microcodeall versions
- netapp clustered data ontapall versions
- netapp hci compute node biosall versions
- netapp hci storage node biosall versions
- netapp solidfire biosall versions
- siemens simatic field pg m5 firmwarebefore 22.01.08
- siemens simatic field pg m6 firmwareall versions
- siemens simatic ipc427e firmwarebefore 21.01.15
- siemens simatic ipc477e firmwarebefore 21.01.15
- siemens simatic ipc477e pro firmwarebefore 21.01.15
- siemens simatic ipc627e firmwarebefore 25.02.08
- siemens simatic ipc647e firmwarebefore 25.02.08
- siemens simatic ipc677e firmwarebefore 25.02.08
- siemens simatic ipc847e firmwarebefore 25.02.08
- siemens simatic itp1000 firmwarebefore 23.01.08
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
- See referencesaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.13 | intel-ucode | before 20201112-r0 | 20201112-r0 |
| Alpine:v3.13 | intel-ucode | before 20210216-r0 | 20210216-r0 |
| Alpine:v3.13 | intel-ucode | before 20201110-r0 | 20201110-r0 |
| Debian:12 | intel-microcode | before 3.20201110.1 | 3.20201110.1 |
| Debian:9 | intel-microcode | before 3.20201118.1~deb9u1 | 3.20201118.1~deb9u1 |
| openSUSE:Leap 15.1 | ucode-intel | before 20201118-lp151.2.33.1 | 20201118-lp151.2.33.1 |
| openSUSE:Leap 15.2 | ucode-intel | before 20201118-lp152.2.8.1 | 20201118-lp152.2.8.1 |
| openSUSE:Tumbleweed | ucode-intel | before 20210608-1.2 | 20210608-1.2 |
| Red Hat:enterprise_linux:6::client | microcode_ctl | before 2:1.17-33.31.el6_10 | 2:1.17-33.31.el6_10 |
| Red Hat:enterprise_linux:6::client | microcode_ctl-debuginfo | before 2:1.17-33.31.el6_10 | 2:1.17-33.31.el6_10 |
| Red Hat:enterprise_linux:7::client | microcode_ctl | before 2:2.1-73.2.el7_9 | 2:2.1-73.2.el7_9 |
| Red Hat:enterprise_linux:7::client | microcode_ctl | before 2:2.1-73.11.el7_9 | 2:2.1-73.11.el7_9 |
| Red Hat:enterprise_linux:7::client | microcode_ctl-debuginfo | before 2:2.1-73.2.el7_9 | 2:2.1-73.2.el7_9 |
| Red Hat:enterprise_linux:7::client | microcode_ctl-debuginfo | before 2:2.1-73.11.el7_9 | 2:2.1-73.11.el7_9 |
| Red Hat:enterprise_linux:8::baseos | microcode_ctl | before 4:20200609-2.20201027.1.el8_3 | 4:20200609-2.20201027.1.el8_3 |
| Red Hat:enterprise_linux:8::baseos | microcode_ctl | before 4:20210216-1.20210608.1.el8_4 | 4:20210216-1.20210608.1.el8_4 |
| Red Hat:rhel_aus:6.5::server | microcode_ctl | before 2:1.17-17.34.el6_5 | 2:1.17-17.34.el6_5 |
| Red Hat:rhel_aus:6.5::server | microcode_ctl-debuginfo | before 2:1.17-17.34.el6_5 | 2:1.17-17.34.el6_5 |
| Red Hat:rhel_aus:6.6::server | microcode_ctl | before 2:1.17-19.32.el6_6 | 2:1.17-19.32.el6_6 |
| Red Hat:rhel_aus:6.6::server | microcode_ctl-debuginfo | before 2:1.17-19.32.el6_6 | 2:1.17-19.32.el6_6 |
| Red Hat:rhel_aus:7.2::server | microcode_ctl | before 2:2.1-12.39.el7_2 | 2:2.1-12.39.el7_2 |
| Red Hat:rhel_aus:7.2::server | microcode_ctl | before 2:2.1-12.34.el7_2 | 2:2.1-12.34.el7_2 |
| Red Hat:rhel_aus:7.2::server | microcode_ctl-debuginfo | before 2:2.1-12.34.el7_2 | 2:2.1-12.34.el7_2 |
| Red Hat:rhel_aus:7.2::server | microcode_ctl-debuginfo | before 2:2.1-12.39.el7_2 | 2:2.1-12.39.el7_2 |
+34
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-40982Information exposure through microarchitectural state after transient execution in certain vector execution units for some Intel(R) Processo27Monitor
- CVE-2020-24511Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclos26Monitor
- CVE-2020-8696Improper removal of sensitive information before storage or transfer in some Intel(R) Processors may allow an authenticated user to potentia22Monitor
- CVE-2023-23908Improper access control in some 3rd Generation Intel(R) Xeon(R) Scalable processors may allow a privileged user to potentially enable inform17Monitor
- CVE-2020-24512Observable timing discrepancy in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via l13Monitor
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 | 20201110-r0 · Alpine:v3.13 | Package registry (OSV) |
| debian:intel-microcode | 3.20201110.1 · Debian:12 | Package registry (OSV) |
| opensuse:ucode-intel | 20201118-lp152.2.8.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| red hat:microcode_ctl | 2:2.1-73.2.el7_9 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:microcode_ctl-debuginfo | 2:2.1-73.2.el7_9 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| rocky linux:microcode_ctl | 4:20210216-1.20210608.1.el8_4 · Rocky Linux:8 | Package registry (OSV) |
| suse:microcode_ctl | 1.17-102.83.59.1 · SUSE:Linux Enterprise Point of Sale 11 SP3 | Package registry (OSV) |
| suse:ucode-intel | 20201027-2.7.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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-21-0691 · Sep 1, 2021(RedHat Güvenlik Güncellemesi)
- TR-21-0661 · Aug 19, 2021(RedHat Güvenlik Güncellemesi Yayınladı)
- TR-21-0634 · Aug 12, 2021(RedHat Güvenlik Güncellemesi Yayınladı)
- TR-20-940 · Nov 11, 2020(Intel Güvenlik Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-668 · Exposure of Resource to Wrong SphereCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.