Wednesday, January 1, 2025
HomeVulnerabilityIntel Paid $100,000 Reward to Researchers who Discovered Spectre 1.1, 1.2 CPU...

Intel Paid $100,000 Reward to Researchers who Discovered Spectre 1.1, 1.2 CPU Level Vulnerability

Published on

SIEM as a Service

Intel rewarded $100,000 for two security researchers to find the CPU Spectre level critical vulnerability which leads to leak confidential information through microarchitectural side channels.

Newly discovered spectre level vulnerabilities are catogorised as Spectre 1.1, a new Spectre-v1 and Spectre 1.2.

Previously discovered highly critical vulnerabilities Spectre and Meltdown have been made a huge impact in IT sectors and the attack works on mobile devices, personal computers and cloud infrastructure depends on the cloud providers.

- Advertisement - SIEM as a Service

Spectre and Meltdown flaw allow an attacker to steal the data that currently processed on the computer it includes the process of personal photos, Emails, Password manager, instant messages and sensitive documents.

Same as old spectre vulnerabilities, These 2 Spectre 1.1, Spectre 1.2 also affect the CPU which leads to excute the malicious process and take over the previously secured CPU memory.

Both of the attacks leverage the “speculative execution” technique which is used by most modern CPUs to optimize performance.

Spectre 1.1

Newly discovered Spectre 1.1(Bounds check bypass CVE-2017-5753) create speculative buffer overflows by leverages speculative stores. same as traditional buffer overflow, it  can modify data and code pointers.

In this case reserarchers said Data-value attacks can bypass some Spectre-v1 mitigations, either directly or by redirecting control flow.

Attacker can ale to  perform arbitrary speculative code execution using Control-flow attacks and also it bypass the mitigation that was applied on precious speculative-execution attacks in Spectre 1.0.

Intel and ARM has been acknowledged for their vulnerable CPU’S and the AMD didn’t release any statment in this regards.

Spectre 1.2

Researchers said, Spectre1.2(Bounds check bypass on stores – CVE-2018-3693) vulnerability allow to by the read-only Protection and , speculative stores are allowed to overwrite read-only data, code pointers, and code metadata, including vtables.

Also the issue could be exploited by an attacker to bypass the Read/Write PTE flags and write code directly in read-only data memory.

According to the Researchers, We advise users to refer to more user-friendly vendor recommendations for mitigations against speculative buffer overflows or available patches.

MicrosoftRed Hat, Oracle have released security advisories, confirming that they are investigating the issues and potential effects.

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

DrayTek Devices Vulnerability Let Attackers Arbitrary Commands Remotely

The DrayTek Gateway devices, more specifically the Vigor2960 and Vigor300B models, are susceptible to...

New Stealthy Malware Leveraging SSH Over TOR Attacking Ukrainian Military

Researchers recently discovered a malicious campaign targeting Ukrainian military personnel through fake "Army+" application...

CISA Warns of Palo Alto Networks PAN-OS Vulnerability Exploited in Wild

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has issued a high-priority alert on...

US Treasury Department Breach, Hackers Accessed Workstations

The Biden administration confirmed that a Chinese state-sponsored hacking group breached the U.S. Treasury...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

CISA Warns of Palo Alto Networks PAN-OS Vulnerability Exploited in Wild

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has issued a high-priority alert on...

TrueNAS CORE Vulnerability Let Attackers Execute Remote Code

Security researchers Daan Keuper, Thijs Alkemade, and Khaled Nassar from Computest Sector 7 disclosed...

NFS Protocol Security Bypassed To Access Files From Remote Server

The NFS protocol offers authentication methods like AUTH_SYS, which relies on untrusted user IDs,...