CyberHub

CyberHub

@cyberhub.blog

→ News, podcast, subreddit and yt video summaries → CVE alerts → CTF challenges https://www.cyberhub.blog #cybersecurity #hacking #cve #tech #news #ai

523 followers376 following31.7K posts

📌 The Cyber Show Explores IoT Security Risks and Penetration Testing in New Episode https://www.cyberhub.blog/article/27247-the-cyber-show-explores-iot-security-risks-and-penetration-testing-in-new-episode

cyberhub.blogThe Cyber Show Explores IoT Security Risks and Penetration Testing in New EpisodeThis episode of *The Cyber Show* features Ken Munro from Pen Test Partners, who discusses the security risks of connected devices, often referred to as the Internet of Things (IoT). The conversation explores how these devices, from smart TVs to children’s toys, can become vulnerabilities in homes and businesses due to poor security practices. Munro explains that while many manufacturers prioritize speed and functionality over security, the consequences can range from privacy invasions to life-threatening risks, particularly in medical or industrial settings. One of the central topics is the nature of penetration testing (pen testing), where security experts simulate cyberattacks to identify weaknesses in systems. Munro describes how pen testers look for misconfigurations, open ports, or flawed encryption in devices—often finding that developers 'roll their own' security solutions instead of using proven standards. This leads to vulnerabilities, such as unencrypted data transmissions or undocumented backdoors that hackers can exploit. For example, a smart TV was found sending voice recordings to a third-party server in plain text, exposing private conversations. The discussion highlights how even well-intentioned features, like remote support for industrial devices, can become security risks if not properly documented or secured. The episode also delves into the motivations behind insecure IoT devices. Munro argues that most vulnerabilities stem from oversight rather than malicious intent—manufacturers rush products to market without adequate security testing or funding for long-term updates. However, he acknowledges that some companies collect excessive data under vague terms of service, often selling it to brokers. This raises ethical concerns, particularly when sensitive data, such as usage patterns from smart sex toys, could endanger users in regions where certain behaviors are criminalized. The conversation underscores the need for better regulations, like the UK’s Product Security and Telecommunications Infrastructure (PSTI) Bill, which mandates security standards and support lifespans for devices. Yet, enforcement remains a challenge, leaving consumers to navigate a market where security is rarely transparent. Another key focus is the unintended consequences of IoT in sensitive environments, such as healthcare. Munro shares a chilling example of a flawed insulin pump system where hackers could have altered blood sugar readings, leading to fatal doses of insulin. While IoT can enable life-saving innovations like continuous glucose monitoring, the lack of rigorous security testing in medical devices poses severe risks. The episode also touches on 'right to repair' debates, where users are often denied control over their devices due to proprietary software or legal restrictions. Munro advocates for 'everything off by default' policies, where users explicitly enable features like microphones or cameras, and for manufacturers to disclose how long they will support a product’s security updates. Without these measures, devices become liabilities once support ends, leaving users vulnerable to exploits. Finally, the discussion addresses the broader societal impact of IoT, including disinformation and the erosion of privacy. Munro points out how seemingly benign devices, like smart meters, can reveal intimate details about a household’s habits, while CCTV cameras with undocumented audio recording capabilities can turn into surveillance tools. The episode concludes with practical advice for consumers, retailers, and governments. Consumers are urged to research products for past vulnerabilities before purchasing, while retailers should vet suppliers for long-term support commitments. Governments are encouraged to enforce existing regulations and resist industry lobbying that prioritizes speed over security. The overarching message is that IoT security requires a cultural shift—one where manufacturers, regulators, and users all take responsibility for safeguarding data and privacy in an increasingly connected world.

📌 Research Exposes Vulnerabilities in Memory Encryption for Confidential Computing https://www.cyberhub.blog/article/27291-research-exposes-vulnerabilities-in-memory-encryption-for-confidential-computing

cyberhub.blogResearch Exposes Vulnerabilities in Memory Encryption for Confidential ComputingThe video presents research by Yoan Bulck (KU Leuven University) and Yes Master on vulnerabilities in memory encryption technologies used in confidential computing, a security paradigm adopted by major cloud providers and processor vendors like Intel, AMD, IBM, and ARM. The study highlights that while confidential computing relies on processor-level isolation and memory encryption to protect data, industry implementations often sacrifice integrity and freshness protections for scalability, leaving systems vulnerable to physical attacks. Researchers demonstrated two attack methods: 'BadRAM,' which exploits writable Serial Presence Detect (SPD) chips on memory modules to create physical memory aliases, and 'Battering RAM,' a $50 interposer-based attack that flips address bits at runtime to bypass boot-time mitigations. These attacks enabled arbitrary read/write access to protected memory regions, including the extraction of Intel’s hardware provisioning keys from SGX enclaves, compromising the entire scalable SGX ecosystem. The findings were responsibly disclosed to AMD and Intel, though both vendors dismissed physical attacks as out of scope, aligning with a French cybersecurity agency’s assessment that users must implicitly trust cloud providers and their supply chains. The research underscores that hardware-based attacks on confidential computing are now feasible with minimal resources, challenging the security guarantees of widely deployed technologies.

📌 Top 20 Cybersecurity Projects Ranked by Difficulty and Hireability Impact https://www.cyberhub.blog/article/27308-top-20-cybersecurity-projects-ranked-by-difficulty-and-hireability-impact

cyberhub.blogTop 20 Cybersecurity Projects Ranked by Difficulty and Hireability ImpactThe video ranks 20 cybersecurity projects by difficulty (from 'noob' to 'madhat') and evaluates their impact on hireability, learning value, and perceived 'coolness' using a custom scoring system. Key projects include contributing a detection rule to Sigma HQ (difficulty 6/10, hireability 9/10), reverse engineering malware with Yara/Sigma rules (difficulty 10/10, hireability 10/10), and disclosing a real vulnerability for a CVE (hireability 10/10). Tools highlighted include Elastic/Sentinel for log analysis, Ghidra for malware reverse engineering, MISP for threat intel automation, and Azure/AWS for cloud misconfiguration hunting. The presenter, a former hiring manager, emphasizes projects that demonstrate investigation skills (e.g., documenting attack chains) or real-world application (e.g., LLM prompt injection testing, mandated by the EU AI Act). Projects like Active Directory attack/defend labs and OAuth consent phishing demos target enterprise-relevant skills, while automated security tooling (e.g., custom vulnerability scanners) proves engineering capability. Scores for hireability range from 1/10 (portfolio websites) to 10/10 (CVE disclosures), with 'coolness' often inversely correlated to practical value. The video concludes that unique, open-source contributions or hands-on detection engineering work stand out to employers.

📌 Black Hat Presentation Highlights Security Risks in Python's Pickle Serialization and Introduces Saf... https://www.cyberhub.blog/article/27356-black-hat-presentation-highlights-security-risks-in-pythons-pickle-serialization-and-introduces-safer-pickle-tool

cyberhub.blogBlack Hat Presentation Highlights Security Risks in Python's Pickle Serialization and Introduces Safer Pickle ToolThe Black Hat presentation titled *Deal With It* explores security risks in Python’s *pickle* serialization format, widely used in AI/ML and data science for sharing datasets. Presenters George Litvinov and Andrew Johnston, both Google security engineers, demonstrate how unpickling untrusted files enables arbitrary code execution via the *reduce* opcode, which can invoke functions like *os.system*. They evaluate open-source pickle scanners, revealing bypass techniques such as invalid opcodes, nested pickles, and string reconstruction to evade detection. Their tool, *Safer Pickle*, addresses these gaps with a two-tiered architecture—emulating calls with dummy modules and performing opcode-level analysis—while allowing customizable allow/deny lists. The tool achieves ~10 MB/s scanning speed and integrates with VirusTotal, though the presenters emphasize that *pickle* remains inherently unsafe, recommending alternatives like *safe tensors*. Key takeaways include tailoring security solutions to specific environments and avoiding over-permissive allow lists. The project is open-source on GitHub under *Google/safer-pickle*.