#iip_updates . Click on this https://informationispowah.blogspot.com/2023/05/new-bruteprint-attack-lets-attackers.html link to read more.
#Information_is_Power .
#we_inform_the_uninformed .
Researchers have discovered an inexpensive attack technique that could be leveraged to brute-force fingerprints on smartphones to bypass user authentication and seize control of the devices.
The approach, dubbed BrutePrint, bypasses limits put in place to counter failed biometric authentication attempts by weaponizing two zero-day vulnerabilities in the smartphone fingerprint authentication (SFA) framework.
The flaws, Cancel-After-Match-Fail (CAMF) and Match-After-Lock (MAL), leverage logical defects in the authentication framework, which arises due to insufficient protection of fingerprint data on the Serial Peripheral Interface (SPI) of fingerprint sensors.
The result is a “hardware approach to do man-in-the-middle (MitM) attacks for fingerprint image hijacking,” researchers Yu Chen and Yiling He said in a research paper. “BrutePrint acts as a middleman between fingerprint sensor and TEE [Trusted Execution Environment].”
The goal, at its core, is to be able to perform an unlimited number of fingerprint image submissions until there is a match. It, however, presupposes that a threat actor is already in possession of the target device in question.
Additionally, it requires the adversary to be in possession of a fingerprint database and a setup comprising a microcontroller board and an auto-clicker that can hijack data sent by a fingerprint sensor to pull off the attack for as low as $15.
The first of the two vulnerabilities that render this attack possible is CAMF, which allows for increasing the fault tolerance capabilities of the system by invalidating the checksum of the fingerprint data, thereby giving an attacker unlimited tries.
MAL, on the other hand, exploits a side-channel to infer matches of the fingerprint images on the target devices, even when it enters a lockout mode following too many repeated login attempts.
“Although the lockout mode is further checked in Keyguard to disable unlocking, the authentication result has been made by TEE,” the researchers explained.
“As Success authentication result is immediately returned when a matched sample is met, it’s possible for side-channel attacks to infer the result from behaviors such as response time and the number of acquired images.”
In an experimental setup, BrutePrint was evaluated against 10 different smartphone models from Apple, Huawei, OnePlus, OPPO, Samsung, Xiaomi, and vivo, yielding infinite attempts on Android and HarmonyOS, and 10 additional attempts on iOS devices.
The findings come as a group of academics detailed a hybrid side-channel that takes advantage of the “three-way tradeoff between execution speed (i.e., frequency), power consumption, and temperature” in modern system-on-chips (SoCs) and GPUs to conduct “browser-based pixel stealing and history sniffing attacks” against Chrome 108 and Safari 16.2.
The attack, called Hot Pixels, takes advantage of this behavior to mount website fingerprinting attacks and employ JavaScript code to harvest a user’s browsing history.
This is accomplished by designing a computationally heavy SVG filter to leak pixel colors by measuring the rendering times and stealthily harvest the information with an accuracy as high as 94%.
The issues have been acknowledged by Apple, Google, AMD, Intel, Nvidia, Qualcomm. The researchers also recommend “prohibiting SVG filters from being applied to iframes or hyperlinks” and preventing unprivileged access to sensor readings.
BrutePrint and Hot Pixels also follow Google’s discovery of 10 security defects in Intel’s Trust Domain Extensions (TDX) that could lead to arbitrary code execution, denial-of-service conditions, and loss of integrity.
On a related note, Intel CPUs have also been found susceptible to a side-channel attack that makes use of variations in execution time caused by changing the EFLAGS register during transient execution to decode data without relying on the cache.
http://dlvr.it/SprXMw
Comments
Post a Comment