{"id":160597,"date":"2026-02-11T17:11:57","date_gmt":"2026-02-11T15:11:57","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/uyazvimost-pozvolyayushhaya-obojti-mehanizm-zashhity-intel-tdx"},"modified":"2026-02-11T17:11:57","modified_gmt":"2026-02-11T15:11:57","slug":"uyazvimost-pozvolyayushhaya-obojti-mehanizm-zashhity-intel-tdx","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/novosti-interneta\/uyazvimost-pozvolyayushhaya-obojti-mehanizm-zashhity-intel-tdx","title":{"rendered":"Vulnerability allowing bypassing Intel TDX protection mechanism","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Google and Intel have revealed the results (PDF) of their collaborative security audit on the Intel TDX 1.5 (Trusted Domain Extensions) mechanism. The Intel TDX technology implements memory encryption for virtual machines to protect them from interference and analysis by the host system administrator, as well as physical attacks on the hardware. The audit identified 6 vulnerabilities and 35 non-security-related issues. <\/p>\n

The issues affect Intel Xeon 6 CPUs, as well as the 4th and 5th generations of Intel Xeon Scalable processors. The vulnerabilities have been addressed in yesterday's microcode update. A toolkit for exploiting vulnerabilities in Intel TDX and prototypes of exploits for two vulnerabilities (CVE-2025-30513, CVE-2025-32007) has been published on GitHub. <\/p>\n

K\u00f5ige ohtlikum haavatavus (CVE-2025-30513) v\u00f5imaldab usaldusv\u00e4\u00e4rsel adminitraatoril, kellel on juurdep\u00e4\u00e4s host-s\u00fcsteemile, saavutada privileegide t\u00f5stmine ja t\u00e4ielikult kompromiteerida Intel TDX tehnoloogia poolt pakutavad turvagarantiid. Haavatavus tuleneb v\u00f5itlusest TDX moodulites, mis v\u00f5imaldab virtuaalmasina r\u00e4nde ajal t\u00f5sta kaitstud keskkonna (TD \u2014 Trusted Domain) olekut migreerimisest debug-re\u017eiimi. <\/p>\n

Probleem tuleneb keskkonna atribuutide asendamise v\u00f5imalusest p\u00e4rast nende kontrollimist, kuid enne nende viimist muudetud olekusse edasi kantud keskkonnas. P\u00e4rast t\u00f5rkeotsingu atribuudi seadistamist saab host-s\u00fcsteemi administraator reaalajas j\u00e4lgida kaitstud k\u00fclgkasutaja s\u00fcsteemi tegevust ja p\u00e4\u00e4seda juurde dekr\u00fcpteeritud m\u00e4lu olekule. <\/p>\n

Haavatavus on piisavalt lihtne \u00e4ra kasutada, kuna administraator saab igal ajal alustada kaitstud virtuaalse masina live-migreerimise protsessi. Probleem tuvastati Google'i teadlaste poolt, kes API-d uurides p\u00f6\u00f6rasid t\u00e4helepanu vastuolule selle vahel, kuidas FSM-is (l\u00f5pliku oleku masinas) j\u00e4lgitakse operatsioonide olekut, t\u00f6\u00f6deldakse impordioperatsiooni katkestamist ja muudetakse, kuid ei taastata algsesse olekusse p\u00e4rast riket, kaitstud keskkonna olek. <\/p>\n

V\u00e4hem ohtlikud haavatavused: <\/p>\n