topic Re:How to solve the IAS authentication display vulnerability INTEL-SA-00615 after applying the latest T in Intel® Software Guard Extensions (Intel® SGX)

How to solve the IAS authentication display vulnerability INTEL-SA-00615 after applying the latest T

koreasoft — Thu, 09 Feb 2023 18:06:04 GMT

1. The latest kernel of ubuntu 20.04 is installed

root@work-machine:~# uname -rs
Linux 5.4.0-139-generic
root@work-machine:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.5 LTS
Release: 20.04
Codename: focal

2. Intel's latest bios ucode microcode is installed

root@work-machine:~# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 6
On-line CPU(s) list: 0-5
Thread(s) per core: 1
Core(s) per socket: 6
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 165
Model name: Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
Stepping: 3
Frequency boost: enabled
CPU MHz: 804.275
CPU max MHz: 2901.0000
CPU min MHz: 800.0000
BogoMIPS: 5799.77
Virtualization: VT-x
L1d cache: 192 KiB
L1i cache: 192 KiB
L2 cache: 1.5 MiB
L3 cache: 12 MiB
NUMA node0 CPU(s): 0-5
Vulnerability Itlb multihit: KVM: Vulnerable
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Mmio stale data: Mitigation; Clear CPU buffers; SMT disabled
Vulnerability Retbleed: Mitigation; Enhanced IBRS
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds: Mitigation; Microcode
Vulnerability Tsx async abort: Not affected
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art
arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 s
se4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr
_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves
dtherm ida arat pln pts md_clear flush_l1d arch_capabilities
root@work-machine:~# dmesg |grep microcode
[ 0.687849] microcode: sig=0xa0653, pf=0x2, revision=0xf4
[ 0.688878] microcode: Microcode Update Driver: v2.2.

3. The latest Intel SGX SDK and Driver are installed

root@work-machine:~# apt list installed libsgx*
Listing... Done
libsgx-ae-epid/unknown 2.18.101.1-focal1 amd64
libsgx-ae-id-enclave/unknown 1.15.100.3-focal1 amd64
libsgx-ae-le/unknown,now 2.18.101.1-focal1 amd64 [installed,automatic]
libsgx-ae-pce/unknown 2.18.101.1-focal1 amd64
libsgx-ae-qe3/unknown 1.15.100.3-focal1 amd64
libsgx-ae-qve/unknown 1.15.100.3-focal1 amd64
libsgx-ae-tdqe/unknown 1.15.100.3-focal1 amd64
libsgx-aesm-ecdsa-plugin-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-aesm-ecdsa-plugin/unknown 2.18.101.1-focal1 amd64
libsgx-aesm-epid-plugin-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-aesm-epid-plugin/unknown 2.18.101.1-focal1 amd64
libsgx-aesm-launch-plugin-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-aesm-launch-plugin/unknown,now 2.18.101.1-focal1 amd64 [installed,automatic]
libsgx-aesm-pce-plugin-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-aesm-pce-plugin/unknown 2.18.101.1-focal1 amd64
libsgx-aesm-quote-ex-plugin-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-aesm-quote-ex-plugin/unknown 2.18.101.1-focal1 amd64
libsgx-dcap-default-qpl-dbgsym/unknown 1.15.100.3-focal1 amd64
libsgx-dcap-default-qpl-dev/unknown 1.15.100.3-focal1 amd64
libsgx-dcap-default-qpl/unknown 1.15.100.3-focal1 amd64
libsgx-dcap-ql-dbgsym/unknown 1.15.100.3-focal1 amd64
libsgx-dcap-ql-dev/unknown 1.15.100.3-focal1 amd64
libsgx-dcap-ql/unknown 1.15.100.3-focal1 amd64
libsgx-dcap-quote-verify-dbgsym/unknown 1.15.100.3-focal1 amd64
libsgx-dcap-quote-verify-dev/unknown 1.15.100.3-focal1 amd64
libsgx-dcap-quote-verify/unknown 1.15.100.3-focal1 amd64
libsgx-enclave-common-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-enclave-common-dev/unknown 2.18.101.1-focal1 amd64
libsgx-enclave-common/unknown,now 2.18.101.1-focal1 amd64 [installed]
libsgx-epid-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-epid-dev/unknown 2.18.101.1-focal1 amd64
libsgx-epid/unknown 2.18.101.1-focal1 amd64
libsgx-headers/unknown 2.18.101.1-focal1 amd64
libsgx-launch-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-launch-dev/unknown 2.18.101.1-focal1 amd64
libsgx-launch/unknown,now 2.18.101.1-focal1 amd64 [installed,automatic]
libsgx-pce-logic-dbgsym/unknown 1.15.100.3-focal1 amd64
libsgx-pce-logic/unknown 1.15.100.3-focal1 amd64
libsgx-qe3-logic-dbgsym/unknown 1.15.100.3-focal1 amd64
libsgx-qe3-logic/unknown 1.15.100.3-focal1 amd64
libsgx-quote-ex-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-quote-ex-dev/unknown 2.18.101.1-focal1 amd64
libsgx-quote-ex/unknown 2.18.101.1-focal1 amd64
libsgx-ra-network-dbgsym/unknown 1.15.100.3-focal1 amd64
libsgx-ra-network-dev/unknown 1.15.100.3-focal1 amd64
libsgx-ra-network/unknown 1.15.100.3-focal1 amd64
libsgx-ra-uefi-dbgsym/unknown 1.15.100.3-focal1 amd64
libsgx-ra-uefi-dev/unknown 1.15.100.3-focal1 amd64
libsgx-ra-uefi/unknown 1.15.100.3-focal1 amd64
libsgx-tdx-logic-dbgsym/unknown 1.15.100.3-focal1 amd64
libsgx-tdx-logic-dev/unknown 1.15.100.3-focal1 amd64
libsgx-tdx-logic/unknown 1.15.100.3-focal1 amd64
libsgx-uae-service-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-uae-service/unknown 2.18.101.1-focal1 amd64
libsgx-urts-dbgsym/unknown 2.18.101.1-focal1 amd64
libsgx-urts/unknown 2.18.101.1-focal1 amd64

4. Hyper-threading option in BIOS is turned off

root@work-machine:~# dmidecode -t processor
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.

Handle 0x0047, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i5
Manufacturer: Intel(R) Corporation
ID: 53 06 0A 00 FF FB EB BF
Signature: Type 0, Family 6, Model 165, Stepping 3
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
Voltage: 0.8 V
External Clock: 100 MHz
Max Speed: 8300 MHz
Current Speed: 2871 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0044
L2 Cache Handle: 0x0045
L3 Cache Handle: 0x0046
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 6
Core Enabled: 6
Thread Count: 6
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control

root@work-machine:~# cat /proc/cpuinfo |grep "model name"
model name : Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
model name : Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
model name : Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
model name : Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
model name : Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
model name : Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz

However, the latest Intel SGX remote authentication still prompts security vulnerabilities:

isvEnclaveQuoteStatus = SW_HARDENING_NEEDED
advisoryURL = https://security-center.intel.com
advisoryIDs = "INTEL-SA-00334", "INTEL-SA-00615"

I'm confused now and can't find a solution. How can I solve this INTEL-SA-00615 vulnerability?

Re:How to solve the IAS authentication display vulnerability INTEL-SA-00615 after applying the latest T

KFPW_Intel — Fri, 10 Feb 2023 04:53:19 GMT

Hi,

Thank you for your interest in Intel® SGX.

Thank you for providing these information to us, it helps us to understand the issue.

Based on your information, Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz is affected. Refer Software Security Guidance for more information.

According to INTEL-SA-00615 Security Advisory, potential security vulnerabilities in Memory Mapped I/O (MMIO) for some Intel® Processors may allow information disclosure. Intel is releasing firmware updates to mitigate these potential vulnerabilities.

Intel recommends that users of the affected Intel® Processors update to the latest version provided by the system manufacturer that addresses these issues.

Intel® SGX PSW for Windows to version 2.16.100.3 or later:

https://registrationcenter.intel.com/en/products/download/3406/

Intel® SGX SDK for Windows to version 2.16.100.3 or later:

https://registrationcenter.intel.com/en/products/download/3407/

Intel® SGX DCAP for Windows to version 1.14.100.3 or later:

https://registrationcenter.intel.com/en/products/download/3610/

Intel® SGX PSW for Linux to version 2.17.100.3 or later:

https://01.org/intel-software-guard-extensions/downloads

Intel® SGX SDK for Linux to version 2.17.100.3 or later:

https://01.org/intel-software-guard-extensions/downloads

Intel® SGX DCAP for Linux to version 1.14.100.3 or later:

https://01.org/intel-software-guard-extensions/downloads

To address this issue, an Intel SGX TCB Recovery is planned. Details can be found here.

Refer to Intel SGX Attestation Technical Details for more information on the Intel SGX TCB recovery process.

Further TCB Recovery Guidance for developers is available

Hope that these information may be useful for you. Inform us if you have any question. Thank you.

Regards,

Ken

Re:How to solve the IAS authentication display vulnerability INTEL-SA-00615 after applying the latest T

KFPW_Intel — Mon, 13 Feb 2023 00:09:36 GMT

Hi,

I hope the information I provided was helpful to you. Do you need further help with this issue?

Please inform us if you have any questions regards to this issue.

Thank you.

Regards,

Ken

Re:How to solve the IAS authentication display vulnerability INTEL-SA-00615 after applying the latest T

KFPW_Intel — Thu, 16 Feb 2023 00:05:42 GMT

Hi,

We have not heard from you in several days so we will no longer monitor this thread. We hope you were able to resolve your issue. Please start a new thread if you need further help.

Regards,

Ken

Re: Re:How to solve the IAS authentication display vulnerability INTEL-SA-00615 after applying the l

alche — Wed, 21 May 2025 18:54:18 GMT

Hi, do I understand right that if all TCB versions "https://api.trustedservices.intel.com/sgx/certification/v4/tcb?fmspc=00606A000000&update=early" contain INTEL-SA-00615 in advisoryIDs then mitigation for INTEL-SA-00615 doesn't exist? Otherwise tcb version without INTEL-SA-00615 would be listed?

Re: Re:How to solve the IAS authentication display vulnerability INTEL-SA-00615 after applying the l

Benny_Intel — Thu, 22 May 2025 15:14:58 GMT

Your understanding is basically correct, but I want to give more details.

As all TCB Levels returned by Intel PCS for this FMSPC include INTEL-SA-00615 in the advisoryIDs, this indicates that no TCB level is available that fully mitigates this advisory in hardware/firmware alone. In other words, there is no microcode or platform update yet that resolves this issue at the TCB level.

However, the status of the newest TCB level is SWHardeningNeeded which means: The issue can be mitigated through software updates (e.g., SGX SDK, PSW, or enclave-level changes).
We provide detailed guidance in INTEL-SA-00615 and in the forum response above.
SWHardeningNeeded is the best possible status in this case, because attestation cannot recognize whether or not the suggested software hardening was applied or not.

Best regards,

Benny

Re: Re:How to solve the IAS authentication display vulnerability INTEL-SA-00615 after applying the l

alche — Thu, 22 May 2025 16:04:10 GMT

Thanks, that’s exactly what I wanted to understand