Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.52% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2020
CVE-2020-8698High confidence
Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access
Unknown · Intel(R) Processors
5.5MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 10 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 4 Aug 2024
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Unknown Intel(R) Processors and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 10 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 10 affected or under-investigation product states without a fixed product state in the same current advisory
Distribution package intelligence
7 package statesRelease-specific package status
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | intel-ucode | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 20201110-r0, 20201112-r0, 20210216-r0 | Alpine Security Database ↗Source updated 23 Oct 2026 |
| Alpine v3.22v3.22 · main | intel-ucode | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 20201110-r0, 20201112-r0, 20210216-r0 | Alpine Security Database ↗Source updated 23 Oct 2026 |
| Alpine v3.21v3.21 · main | intel-ucode | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 20201110-r0, 20201112-r0, 20210216-r0 | Alpine Security Database ↗Source updated 23 Oct 2026 |
| Debian trixietrixie · source | intel-microcode | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.20201110.1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian bookwormbookworm · source | intel-microcode | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.20201110.1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian forkyforky · source | intel-microcode | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.20201110.1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian sidsid · source | intel-microcode | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.20201110.1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
SSA-678983 · CSAF 2.0 · revision 7 · finalSiemens ProductCERTSSA-678983: Vulnerabilities in Industrial PCs and CNC devices using Intel CPUs (November 2020)
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC Field PG M5
- SIMATIC Field PG M6
- SIMATIC IPC427E (incl. SIPLUS variants)
- SIMATIC IPC477E
- SIMATIC IPC477E Pro
- SIMATIC IPC627E
- SIMATIC IPC647E
- SIMATIC IPC677E
- SIMATIC IPC847E
- SIMATIC ITP1000
- Summary
- Improper isolation of shared resources in some Intel Processors may allow an authenticated user to potentially enable information disclosure via local access.
- Remediation
- Update BIOS to V22.01.08 or later version
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 10 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
What
Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
Why
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.
What
Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
Why
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Exposure of Resource to Wrong Sphere → obtain information outside the intended access boundary
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-668 ↗
CWE-668: Exposure of Resource to Wrong Sphere. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 12 Nov 2020 · Last source change 4 Aug 2024, 10:03 UTC · CWE-668 · Exposure of Resource to Wrong Sphere
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2020-29546
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Siemens ProductCERT ↗
- Before
- Awaiting fix
- After
- Mitigation available
CVE published
Remediation guidance recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.