NVD / CVE Program· CNA intel

CVE-2020-8703: Improper buffer restrictions in a subsystem in the Intel(R) CSME versions before 11.8.86, 11.12.86, 11.22.86, 12.0.81, 13.0.47, 13.30.17, 14

Noroxi assessment

Priority: Monitor (action score 26/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.33% (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.
According to the record, no fixed version is available yet.
Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

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 buffer restrictions in a subsystem in the Intel(R) CSME versions before 11.8.86, 11.12.86, 11.22.86, 12.0.81, 13.0.47, 13.30.17, 14.1.53, 14.5.32 and 15.0.22 may allow a privileged user to potentially enable escalation of privilege via local access.

MediumCVSS 6.7 · v3.1—No exploit No fix recorded

Published: Jun 9, 2021
Updated: Jun 16, 2026
EPSS: 0.3% · 26th percentile
CWE: CWE-119

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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	converged security and manageability engine	cpe:2.3:a:intel:converged_security_and_manageability_engine
intel	b360	cpe:2.3:h:intel:b360
intel	b365	cpe:2.3:h:intel:b365
intel	c242	cpe:2.3:h:intel:c242
intel	c246	cpe:2.3:h:intel:c246
intel	celeron 4205u	cpe:2.3:h:intel:celeron_4205u
intel	celeron 4305u	cpe:2.3:h:intel:celeron_4305u
intel	celeron 4305ue	cpe:2.3:h:intel:celeron_4305ue
intel	core i3-8100	cpe:2.3:h:intel:core_i3-8100
intel	core i3-8100b	cpe:2.3:h:intel:core_i3-8100b
intel	core i3-8100h	cpe:2.3:h:intel:core_i3-8100h
intel	core i3-8100t	cpe:2.3:h:intel:core_i3-8100t

and 188 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

intel converged security and manageability enginebefore 12.0.81
intel converged security and manageability enginebefore 13.0.47
intel converged security and manageability enginebefore 13.30.17
intel converged security and manageability enginebefore 14.1.53
intel converged security and manageability enginebefore 14.5.32
intel converged security and manageability enginebefore 11.8.86
intel converged security and manageability enginebefore 11.12.86
intel converged security and manageability enginebefore 11.22.86
intel converged security and manageability enginebefore 15.0.22
netapp cloud backupall versions
siemens simatic field pg m5 firmwareall versions
siemens simatic field pg m6 firmwareall versions
siemens simatic ipc427e firmwareall versions
siemens simatic ipc477e firmwareall versions
siemens simatic ipc477e pro firmwareall versions
siemens simatic ipc527g firmwareall versions
siemens simatic ipc547g firmwareall versions
siemens simatic ipc627e firmwarebefore 25.02.10
siemens simatic ipc647e firmwarebefore 25.02.10
siemens simatic ipc677e firmwarebefore 25.02.10

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) CSME versions
- versions before 11.8.86, 11.12.86, 11.22.86, 12.0.81, 13.0.47, 13.30.17, 14.1.53, 14.5.32 and 15.0.22affected

Same product

intel: all records

Other highest-scoring records for the same primary product.

CVE-2020-12303Use after free in DAL subsystem for Intel(R) CSME versions before 11.8.80, 11.12.80, 11.22.80, 12.0.70, 13.0.40, 13.30.10, 14.0.45 and 14.5.
31Monitor
CVE-2020-12297Improper access control in Installer for Intel(R) CSME Driver for Windows versions before 11.8.80, 11.12.80, 11.22.80, 12.0.70, 13.0.40, 13.
31Monitor
CVE-2020-24516Modification of assumed-immutable data in subsystem in Intel(R) CSME versions before 13.0.47, 13.30.17, 14.1.53, 14.5.32, 15.0.22 may allow
27Monitor

Published before and after this one in the same product

← EarlierCVE-2020-8761Nov 12, 2020 · Inadequate encryption strength in subsystem for Intel(R) CSME versions before 13.0.40 and 13.30.10 may allow an unauthenticated user to pote
18Monitor
← EarlierCVE-2020-24506Jun 9, 2021 · Out of bound read in a subsystem in the Intel(R) CSME versions before 12.0.81, 13.0.47, 13.30.17, 14.1.53 and 14.5.32 may allow a privileged
17Monitor
← EarlierCVE-2020-24507Jun 9, 2021 · Improper initialization in a subsystem in the Intel(R) CSME versions before 11.8.86, 11.12.86, 11.22.86, 12.0.81, 13.0.47, 13.30.17, 14.1.53
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

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 researchers

Finders, 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