Daily Edition · Page 4

THE DAILY INDEX

Technology, AI, software, security, crypto and business

ATTACKS & VULNERABILITIES

TLDR InfoSec

JOOKI - TAKING CONTROL OF A FORGOTTEN DEVICE

This post explores how to revive the abandoned Jooki children's audio players through firmware analysis and discovering exploits after the company's bankruptcy left devices non-functional. The solution uses Mender for software updates and can be controlled through a web interface, enabling customization and potential security risks. The author notes that by understanding its firmware, access points, and potential vulnerabilities, users can interact with Jooki more effectively and securely.

YOU'RE THINKING ABOUT PASSKEYS WRONG

Some in the security community have argued that passkeys have failed at their promise of passwordless authentication and should instead be used as a second factor due to complexities such as account recovery on a new device. The author of this post argues that this reflects an improper way of thinking about passkeys and presents a login/registration flow that uses magic links for new device/registration and then uses passkeys for subsequent access.

FOUNDATIONS FOR MODERN DEFENSIBLE ARCHITECTURE

The Australian Signals Directorate (ASD) has published a modern defensible architecture framework based on zero trust principles ("never trust, always verify," "assume breach," and "verify explicitly") and five key pillars (Identity, Devices, Networks, Applications/Workloads, and Data), emphasizing that organizations should prepare for "when" not "if" a cyber incident occurs. These principles, based on zero trust and secure-by-design practices, aim to enhance cyber resilience and protect critical assets. Organizations can use the Foundations to build a strong security framework adaptable to evolving technologies and threats.

THE RISKS OF USER IMPERSONATION

This article dives deep into user impersonation risks and mitigations, which is a common way to allow logging in as another user. This feature is often implemented by changing the sub property of a JWT but is inherently problematic as it requires maintaining an admin list and securing the feature, is insecure by design, and also muddies audit trails. One possible solution is to add a new claim to the JWT but this is error prone and instead advocates for using DOM recording to collect as much sanitized data about a user's session as possible instead.

TLDR IndexPage 4