Skip to content
Fencer Intel
medium 4.4

CVE-2019-0117 json

Insufficient access control in protected memory subsystem for Intel(R) SGX for 6th, 7th, 8th, 9th Generation Intel(R) Core(TM) Processor Fa…

published 6y ago modified 4mo ago also EUVD-2019-0924

cvss
4.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

Insufficient access control in protected memory subsystem for Intel(R) SGX for 6th, 7th, 8th, 9th Generation Intel(R) Core(TM) Processor Families; Intel(R) Xeon(R) Processor E3-1500 v5, v6 Families; Intel(R) Xeon(R) E-2100 & E-2200 Processor Families with Intel(R) Processor Graphics may allow a privileged user to potentially enable information disclosure via local access.

Patch / fix

  • microcode_ctl RHEL 6 2:1.17-33.19.el6_10
  • microcode_ctl RHEL 7 2:2.1-53.3.el7_7
  • microcode_ctl RHEL 8 4:20190618-1.20191112.1.el8_1
  • microcode_ctl RHEL 6.5 AUS 2:1.17-17.25.el6_5
  • microcode_ctl RHEL 6.6 AUS 2:1.17-19.23.el6_6
  • microcode_ctl RHEL 7.2 TUS, RHEL 7.2 E4S, RHEL 7.2 AUS 2:2.1-12.24.el7_2
  • microcode_ctl RHEL 7.3 TUS, RHEL 7.3 E4S, RHEL 7.3 AUS 2:2.1-16.27.el7_3
  • microcode_ctl RHEL 7.4 TUS, RHEL 7.4 E4S, RHEL 7.4 AUS 2:2.1-22.26.el7_4

red hat advisories RHEA-2019:3854RHEA-2019:3853RHEA-2019:3847RHEA-2019:3852RHEA-2019:3851RHEA-2019:3850

  • intel-ucode Arch Linux 20191112-1

arch linux advisories AVG-1068

Is CVE-2019-0117 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-0117 updated cvss 6.0

hw: Intel SGX information leak

  • Red Hat Enterprise Linux 5 microcode_ctl
    affected: workaround, no fix planned “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.”
  • Red Hat Enterprise Linux BaseOS (v. 8) microcode_ctl 20190618-1.20191112.1.el8_1
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3845
  • Red Hat Enterprise Linux BaseOS E4S (v. 8.0) microcode_ctl 20180807a-2.20191112.1.el8_0
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2020:0635
  • Red Hat Enterprise Linux Client (v. 7) microcode_ctl 2.1-53.3.el7_7 Red Hat Enterprise Linux ComputeNode (v. 7) microcode_ctl 2.1-53.3.el7_7
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3846
  • Red Hat Enterprise Linux ComputeNode EUS (v. 7.5) microcode_ctl 2.1-29.24.el7_5
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3849
  • Red Hat Enterprise Linux ComputeNode EUS (v. 7.6) microcode_ctl 2.1-47.8.el7_6
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3848
  • Red Hat Enterprise Linux Desktop (v. 6) microcode_ctl 1.17-33.19.el6_10 Red Hat Enterprise Linux HPC Node (v. 6) microcode_ctl 1.17-33.19.el6_10 Red Hat Enterprise Linux Server (v. 6) microcode_ctl 1.17-33.19.el6_10
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3847
  • Red Hat Enterprise Linux Server (v. 7) microcode_ctl 2.1-53.3.el7_7
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3846
show 15 more
  • Red Hat Enterprise Linux Server AUS (v. 6.5) microcode_ctl 1.17-17.25.el6_5
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3854
  • Red Hat Enterprise Linux Server AUS (v. 6.6) microcode_ctl 1.17-19.23.el6_6
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3853
  • Red Hat Enterprise Linux Server AUS (v. 7.2) microcode_ctl 2.1-12.24.el7_2
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3852
  • Red Hat Enterprise Linux Server AUS (v. 7.3) microcode_ctl 2.1-16.27.el7_3
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3851
  • Red Hat Enterprise Linux Server AUS (v. 7.4) microcode_ctl 2.1-22.26.el7_4
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3850
  • Red Hat Enterprise Linux Server E4S (v. 7.2) microcode_ctl 2.1-12.24.el7_2
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3852
  • Red Hat Enterprise Linux Server E4S (v. 7.3) microcode_ctl 2.1-16.27.el7_3
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3851
  • Red Hat Enterprise Linux Server E4S (v. 7.4) microcode_ctl 2.1-22.26.el7_4
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3850
  • Red Hat Enterprise Linux Server EUS (v. 7.5) microcode_ctl 2.1-29.24.el7_5
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3849
  • Red Hat Enterprise Linux Server EUS (v. 7.6) microcode_ctl 2.1-47.8.el7_6
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3848
  • Red Hat Enterprise Linux Server TUS (v. 7.2) microcode_ctl 2.1-12.24.el7_2
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3852
  • Red Hat Enterprise Linux Server TUS (v. 7.3) microcode_ctl 2.1-16.27.el7_3
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3851
  • Red Hat Enterprise Linux Server TUS (v. 7.4) microcode_ctl 2.1-22.26.el7_4
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3850
  • Red Hat Enterprise Linux Workstation (v. 6) microcode_ctl 1.17-33.19.el6_10
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3847
  • Red Hat Enterprise Linux Workstation (v. 7) microcode_ctl 2.1-53.3.el7_7
    fixed: vendor fix “As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.” RHEA-2019:3846

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • n/a 2019.2 IPU – Intel(R) SGX with Intel(R) Processor Graphics Update

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.