Two bugs in Intel's TDX guest crate
One TDCALL wrapper discarded a correctly packed RCX value. Another inverted a bitmap validation check. Intel fixed both bugs in tdx-guest 0.3.1.
I am a security researcher. I examine hardware attestation, confidential computing SDKs, TEE quote verifiers, and enclave tools.
One TDCALL wrapper discarded a correctly packed RCX value. Another inverted a bitmap validation check. Intel fixed both bugs in tdx-guest 0.3.1.
I found two privilege-escalation defects in Intel TDX Guest software. Intel rated both issues 4.6 Medium and corrected them in version 0.3.1. The assessment requires a local, highly privileged attacker.
I found an out-of-bounds read in the Open Enclave SDK quote parser. Unguarded pointer arithmetic read an attacker-controlled SGX quote buffer. Microsoft rated the issue Low severity and corrected it in version 0.19.16.
I found an off-by-one mask and incorrect 32-bit zero-extension in the x86/TDX code for port I/O. The patches have my Reported-by credit and a Cc stable tag.
I wrote the fix for a double free in the vectorized receive recovery path of NVIDIA mlx5. NVIDIA reviewed and approved the fix. DPDK backported it to the 25.11 stable branch.
I reported missing server authentication in the salmiac KMS client. The defect let an untrusted Nitro parent get the LUKS2 passphrase. Fortanix corrected the defect in pull request 106 and gave me credit in a private advisory.
Intel accepted four additional reports for attestation software and key broker software. Intel has not published the details. I keep the details private during coordinated disclosure.