Apple Watch | Breaking Cybersecurity News | The Hacker News

Apple has released out-of-band patches for iOS, macOS, watchOS, and Safari web browser to address a security flaw that could allow attackers to run arbitrary code on devices via malicious web content. Tracked as CVE-2021-1844 , the vulnerability was discovered and reported to the company by Clément Lecigne of Google's Threat Analysis Group and Alison Huffman of Microsoft Browser Vulnerability Research. According to the update notes posted by Apple, the flaw stems from a memory corruption issue that could lead to arbitrary code execution when processing specially crafted web content. The company said the problem was addressed with "improved validation." The update is available for devices running  iOS 14.4, iPadOS 14.4 ,  macOS Big Sur , and  watchOS 7.3.1  (Apple Watch Series 3 and later), and as an  update to Safari  for MacBooks running macOS Catalina and macOS Mojave. The latest development comes on the heels of a patch for  three zero-day vulnerabilities  (CVE-

Credit: mirror.co.uk If you love wearing tattoos and have one on your wrist, then the Apple Watch won't work for you. Yes, you heard that right. Apple watch is unable to figure out your blood pressure or even sense your skin contact if you wear the watch on a tattooed wrist. Generally, the Apple Watch automatically detects your wrist by your measuring your heart's pulse rate. So, you don't need to enter a password every time you put the watch on your wrist. The issue with the Apple Watch: However, the infrared sensors of the Apple Watch that enable wrist detection often fail when encountered by dark ink tattoos or scars. Many users on Twitter and Reddit have complained online that their Apple watches doesn't play nice when worn on a tattooed wrist. The watch's heart rate sensor loses the connection and gives inaccurate readings, even the device fails to detect direct contact with the user's skin, causing apps to shut down and repeatedly as

Identities now transcend human boundaries. Within each line of code and every API call lies a non-human identity. These entities act as programmatic access keys, enabling authentication and facilitating interactions among systems and services, which are essential for every API call, database query, or storage account access. As we depend on multi-factor authentication and passwords to safeguard human identities, a pressing question arises: How do we guarantee the security and integrity of these non-human counterparts? How do we authenticate, authorize, and regulate access for entities devoid of life but crucial for the functioning of critical systems? Let's break it down. The challenge Imagine a cloud-native application as a bustling metropolis of tiny neighborhoods known as microservices, all neatly packed into containers. These microservices function akin to diligent worker bees, each diligently performing its designated task, be it processing data, verifying credentials, or