{"id":1053,"date":"2018-05-22T14:03:08","date_gmt":"2018-05-22T14:03:08","guid":{"rendered":"https:\/\/kasperskycontenthub.com\/threatpost\/?p=132169"},"modified":"2018-05-22T14:03:08","modified_gmt":"2018-05-22T14:03:08","slug":"intel-responds-to-spectre-like-flaw-in-cpus","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/","title":{"rendered":"Intel Responds to Spectre-Like Flaw In CPUs"},"content":{"rendered":"
<\/div>\n
<\/div>\n

Intel acknowledged that its processors are vulnerable to another dangerous speculative execution side channel flaw that could give attackers\u00a0unauthorized read access to memory.<\/p>\n

The new vulnerability, disclosed by Google Project Zero and Microsoft\u2019s Security Response Center, is called Variant 4, and potentially enables attackers to read privileged data across trust boundaries. That\u2019s similar to two side channel analysis vulnerabilities, Meltdown and Spectre, Intel faced earlier this year<\/a> in its server and\u00a0desktop processors.<\/p>\n

Variant 4 (CVE-2018-3639<\/a>) is also a side channel analysis security flaw, but it uses a different process to extract information, and the most common use is in web browsers.<\/p>\n

\u201cLike the other GPZ variants, Variant 4 uses speculative execution, a feature common to most modern processor architectures, to potentially expose certain kinds of data through a side channel,\u201d Leslie Culbertson, executive vice president and general manager of Product Assurance and Security at\u00a0Intel, said in a post<\/a>\u00a0on Monday. \u201cIn this case, the researchers demonstrated Variant 4 in a language-based runtime environment.\u00a0 While we are not aware of a successful browser exploit, the most common use of runtimes, like JavaScript, is in web browsers.\u201d<\/p>\n

Almost 50 Intel processor brands are impacted by the newest vulnerability, including Intel\u2019s Atom, Core and Xeon lineups. However, the chip company said it hasn\u2019t seen any real-world exploits of the new variant.\u00a0Intel also disclosed a Rogue System Register Read\u00a0vulnerability (CVE-2018-3640<\/a>) called Variant 3a.<\/p>\n

Variant 4, similar to other Spectre vulnerabilities, stems from a glitch in Intel-based products. Essentially microprocessors use speculative execution and speculative execution of memory to read before the addresses of all prior memory writes are known. This enables an attacker with local user access using a side-channel analysis (aka Variant 4) to gain unauthorized disclosure of information.<\/p>\n

Google Project Zero\u2019s Jann Horn and Microsoft\u2019s Ken Johnson first reported Variant 4.<\/p>\n

Horn said in a post<\/a> that he first set on track to discovering Variant 4 after noticing \u00a0Intel\u2019s Optimization Manual (in section 2.4.4.5, regarding \u201cmemory disambiguation\u201d) said that:<\/p>\n

\n

\u201cA load instruction micro-op may depend on a preceding store. Many microarchitectures block loads until all preceding store address are known.<\/p>\n

The memory disambiguator predicts which loads will not depend on any previous stores. When the disambiguator predicts that a load does not have such a dependency, the load takes its data from the L1 data cache. Eventually, the prediction is verified. If an actual conflict is detected, the load and all succeeding instructions are re-executed.\u201d<\/p>\n<\/blockquote>\n

After further experiments, Horn said this effect can be used to cause speculative execution to \u201ccontinue far enough to execute a Spectre-style gadget on a pointer read from a memory slot to which a store has been speculatively ignored.\u201d<\/p>\n

Essentially, Horn found that Variant 4 could be exploited by program scripts in order to access data stored elsewhere in a program \u2013 enabling attackers running a script in a browser to read data from another browser tab.<\/p>\n

In a security advisory, Microsoft\u00a0<\/a>said that the new variant could allow an attacker to read privileged data across trust boundaries, and can be exploited through vulnerable code patterns in the operating system (OS) or in applications could allow an attacker to exploit this vulnerability.<\/p>\n

\u201cIn the case of Just-in-Time (JIT) compilers, such as JavaScript JIT employed by modern web browsers, it may be possible for an attacker to supply JavaScript that produces native code that could give rise to an instance of CVE-2018-3639,\u201d said Microsoft. \u201cHowever, Microsoft Edge, Internet Explorer, and other major browsers have taken steps to increase the difficulty of successfully creating a side channel.\u201d<\/p>\n

Intel rated the new vulnerability as a \u201cmoderate<\/a>\u201d risk because starting in January most leading browser providers \u2013 like Safari, Edge and Chrome \u2013 all patched for Meltdown in their managed runtimes, and \u201cthese mitigations are also applicable to variant 4 and available for consumers to use today,\u201d Intel said.<\/p>\n

However, the company said it will still release a full mitigation option in the coming weeks\u00a0to \u201cprevent this method from being used in other ways.\u201d<\/p>\n

Vendor Mitigations<\/strong><\/p>\n

An array of vendors have responded to Variant 4.\u00a0Red Hat\u00a0<\/a>said in a post that \u201cRed Hat Product Security is aware of this issue. Updates will be released as they become available.\u201d<\/p>\n

AMD recommended customers check for mitigations<\/a> being provided by operating system updates back to its Bulldozer lineup: \u201cMicrosoft is completing final testing and validation of AMD-specific updates for Windows client and server operating systems, which are expected to be released through their standard update process,\u201d it said in an advisory.\u00a0 \u201cSimilarly, Linux distributors are developing operating system updates for SSB. AMD recommends checking with your OS provider for specific guidance on schedules.\u201d<\/p>\n

ARM stressed that the majority<\/a> of its processors are not impacted by any side-channel flaw variant; however, several specific models, including Cortex-A17 and Cortex-A75, may be.<\/p>\n

IBM, meanwhile said that mitigation for Variant 4 will impact Power Systems clients. Customers need to install patches to both system firmware and operating systems, according to IBM: \u201cBoth the firmware and OS patches are required for the mitigation to be effective against these vulnerabilities and the latest firmware and OS patches incorporate mitigations for the fourth variant,\u201d it said in a post<\/a>. Firmware patches for POWER7, POWER7+, POWER8 and POWER9 platforms are now available.<\/p>\n

Patching and Performance<\/strong><\/p>\n

Intel said the vulnerability mitigations (coined as Speculative Store Bypass Disable, or SSBD) for Variant 4 will be released by OEM system manufacturers and system software vendors in the coming weeks. Similar to earlier in the year, the fixes for the flaw could also impact performance by between 2 and 8 percent for certain systems.<\/p>\n

\u201cIn this configuration, we have observed no performance impact. If enabled, we\u2019ve observed a performance impact of approximately 2 to 8 percent based on overall scores for benchmarks like SYSmark 2014 SE and SPEC integer rate on client\u00a0and server test systems,\u201d Culbertson said in her post.<\/p>\n

The same update also includes microcode that addresses Variant 3a (Rogue System Register Read), Intel said. \u201cWe have not observed any meaningful performance impact on client or server benchmarks with the Variant 3a mitigation,\u201d Culbertson said.<\/p>\n

Spectre and Meltdown also infamously faced messy patching efforts<\/a>\u00a0across the industry in the wake of the vulnerability disclosure. Intel initially released patches addressing the Spectre and Meltdown vulnerabilities in January, but later yanked its patches for the Variant 2\u00a0flaw \u2013 both for client compute and data center chips \u2013 after acknowledging that they caused \u201chigher than expected reboots and other unpredictable system behavior.\u201d<\/p>\n

Industry Reaction<\/strong><\/p>\n

The new vulnerability comes as no surprise to the industry, especially with rumors swirling<\/a> that new Spectre-like flaws would be disclosed by German magazine c\u2019t earlier in May.<\/p>\n

However, beyond that, industry experts such as Renaud Deraison, co-founder and CTO of Tenable, think that the tech world is moving headfirst into making chips \u00a0quicker and more efficient \u2013 \u00a0so quick, in fact, that they are prioritizing speed over security.<\/p>\n

\u201cWe as an industry have trained people to expect speed,\u201d Deraison said. \u201cThe speed of the chips inside our personal computers, our tablets and our phones is critical to their performance \u2014 everybody knows that. In this case, the vulnerabilities take advantage of the very features that make them fast. Intel optimized for performance and later learned they were facing a trade off between security and performance. The vast majority of people would choose speed over security, too.\u201d<\/p>\n

READ MORE HERE<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Intel on Monday acknowledged that its processors are vulnerable to another Spectre-like speculative execution side channel flaw that could allow attackers to access information. READ MORE HERE…<\/p>\n","protected":false},"author":2,"featured_media":1054,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"colormag_page_layout":"default_layout","footnotes":""},"categories":[3],"tags":[290,65,659,67,660,68,254,661,19,55,69],"class_list":["post-1053","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-threatpost","tag-google-project-zero","tag-intel","tag-intel-flaw","tag-meltdown","tag-side-channel-analysis","tag-spectre","tag-uncategorized","tag-variant-4","tag-vulnerabilities","tag-vulnerability","tag-web-security"],"yoast_head":"\nIntel Responds to Spectre-Like Flaw In CPUs 2026 | ThreatsHub Cybersecurity News<\/title>\n<meta name=\"description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Intel Responds to Spectre-Like Flaw In CPUs 2026 | ThreatsHub Cybersecurity News\" \/>\n<meta property=\"og:description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/\" \/>\n<meta property=\"og:site_name\" content=\"ThreatsHub Cybersecurity News\" \/>\n<meta property=\"article:published_time\" content=\"2018-05-22T14:03:08+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/intel-responds-to-spectre-like-flaw-in-cpus.png\" \/>\n\t<meta property=\"og:image:width\" content=\"680\" \/>\n\t<meta property=\"og:image:height\" content=\"400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"TH Author\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@threatshub\" \/>\n<meta name=\"twitter:site\" content=\"@threatshub\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"TH Author\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/\"},\"author\":{\"name\":\"TH Author\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\"},\"headline\":\"Intel Responds to Spectre-Like Flaw In CPUs\",\"datePublished\":\"2018-05-22T14:03:08+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/\"},\"wordCount\":1226,\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/05\\\/intel-responds-to-spectre-like-flaw-in-cpus.png\",\"keywords\":{\"0\":\"Google Project Zero\",\"1\":\"Intel\",\"2\":\"intel flaw\",\"3\":\"Meltdown\",\"4\":\"Side channel analysis\",\"5\":\"Spectre\",\"7\":\"Variant 4\",\"8\":\"Vulnerabilities\",\"9\":\"Vulnerability\",\"10\":\"Web Security\"},\"articleSection\":[\"Threatpost\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/\",\"name\":\"Intel Responds to Spectre-Like Flaw In CPUs 2026 | ThreatsHub Cybersecurity News\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/05\\\/intel-responds-to-spectre-like-flaw-in-cpus.png\",\"datePublished\":\"2018-05-22T14:03:08+00:00\",\"description\":\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/05\\\/intel-responds-to-spectre-like-flaw-in-cpus.png\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/05\\\/intel-responds-to-spectre-like-flaw-in-cpus.png\",\"width\":680,\"height\":400},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/intel-responds-to-spectre-like-flaw-in-cpus\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Google Project Zero\",\"item\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/tag\\\/google-project-zero\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Intel Responds to Spectre-Like Flaw In CPUs\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"name\":\"ThreatsHub Cybersecurity News\",\"description\":\"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"alternateName\":\"Threatshub.org\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\",\"name\":\"ThreatsHub.org\",\"alternateName\":\"Threatshub.org\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"width\":432,\"height\":435,\"caption\":\"ThreatsHub.org\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/threatshub\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\",\"name\":\"TH Author\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"caption\":\"TH Author\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Intel Responds to Spectre-Like Flaw In CPUs 2026 | ThreatsHub Cybersecurity News","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/","og_locale":"en_US","og_type":"article","og_title":"Intel Responds to Spectre-Like Flaw In CPUs 2026 | ThreatsHub Cybersecurity News","og_description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","og_url":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/","og_site_name":"ThreatsHub Cybersecurity News","article_published_time":"2018-05-22T14:03:08+00:00","og_image":[{"width":680,"height":400,"url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/intel-responds-to-spectre-like-flaw-in-cpus.png","type":"image\/png"}],"author":"TH Author","twitter_card":"summary_large_image","twitter_creator":"@threatshub","twitter_site":"@threatshub","twitter_misc":{"Written by":"TH Author","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/#article","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/"},"author":{"name":"TH Author","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476"},"headline":"Intel Responds to Spectre-Like Flaw In CPUs","datePublished":"2018-05-22T14:03:08+00:00","mainEntityOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/"},"wordCount":1226,"publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/#primaryimage"},"thumbnailUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/intel-responds-to-spectre-like-flaw-in-cpus.png","keywords":{"0":"Google Project Zero","1":"Intel","2":"intel flaw","3":"Meltdown","4":"Side channel analysis","5":"Spectre","7":"Variant 4","8":"Vulnerabilities","9":"Vulnerability","10":"Web Security"},"articleSection":["Threatpost"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/","url":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/","name":"Intel Responds to Spectre-Like Flaw In CPUs 2026 | ThreatsHub Cybersecurity News","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/#primaryimage"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/#primaryimage"},"thumbnailUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/intel-responds-to-spectre-like-flaw-in-cpus.png","datePublished":"2018-05-22T14:03:08+00:00","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","breadcrumb":{"@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/#primaryimage","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/intel-responds-to-spectre-like-flaw-in-cpus.png","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/intel-responds-to-spectre-like-flaw-in-cpus.png","width":680,"height":400},{"@type":"BreadcrumbList","@id":"https:\/\/www.threatshub.org\/blog\/intel-responds-to-spectre-like-flaw-in-cpus\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.threatshub.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Google Project Zero","item":"https:\/\/www.threatshub.org\/blog\/tag\/google-project-zero\/"},{"@type":"ListItem","position":3,"name":"Intel Responds to Spectre-Like Flaw In CPUs"}]},{"@type":"WebSite","@id":"https:\/\/www.threatshub.org\/blog\/#website","url":"https:\/\/www.threatshub.org\/blog\/","name":"ThreatsHub Cybersecurity News","description":"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform","publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"alternateName":"Threatshub.org","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.threatshub.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.threatshub.org\/blog\/#organization","name":"ThreatsHub.org","alternateName":"Threatshub.org","url":"https:\/\/www.threatshub.org\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","width":432,"height":435,"caption":"ThreatsHub.org"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/threatshub"]},{"@type":"Person","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476","name":"TH Author","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","caption":"TH Author"}}]}},"_links":{"self":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/1053","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/comments?post=1053"}],"version-history":[{"count":0,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/1053\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media\/1054"}],"wp:attachment":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media?parent=1053"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/categories?post=1053"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/tags?post=1053"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}