Black Hat Asia 2026 | Systematically Exploring and Exploiting DNS Silent Vulnerabilities

Domain names function as human-readable identifiers on the Internet, with characters serving as their essential building blocks. However, since the initial specification of domain names in 1983, the security implications of handling special characters within the domain name resolution process have remained largely overlooked. In this work, we conducted the first systematic study of special character handling logic in DNS, reviewing DNS RFCs and analyzing 31 widely-used DNS software implementations through source code review and gray-box testing. Our systematic analysis reveals two new DNS logic vulnerabilities arising from inconsistencies and silent handling behaviors, leading to two classes of attacks (four variants) that affect all DNS roles, including stub resolvers, forwarders, recursive resolvers, and authoritative nameservers. We name them the SHAR attack. Attackers can exploit these vulnerabilities to launch DNS cache poisoning and load balancing disruption attacks. Through comprehensive experiments, we validated the impact on the real world. All 31 tested mainstream DNS software implementations are vulnerable to SHAR. Notably, attackers can seize control of domain names, even the entire TLD or deceive victim resolvers to return invalid responses for legitimate queries, resulting in a persistent DoS effect. The SHAR attack can also enhance 10/13 well-known off-path DNS cache poisoning attacks (2002–2025). To further determine the impact in the wild, we test all DNS-related roles, including mainstream Wi-Fi routers, router OSes, public DNS services, table open DNS resolvers, Root servers, TLD servers, SLD servers, and domain names. The results show that the SHAR attack affects all tested Wi-Fi routers, router OSes, and public DNS services. In addition, we identified that over 12.5M domain names are also vulnerable to the SHAR attack. Following the best practice of responsible disclosure, we have reported these vulnerabilities to all affected vendors. Fasheng Miao | Master Student, Tsinghua University Xiang Li | Associate Professor, Nankai University Changqing An | Associate Researcher, Tsinghua University Jilong Wang | Professor, Tsinghua University https://ift.tt/Y5SJER7

source https://www.youtube.com/watch?v=2Euva5ZT-cA

Black Hat Asia 2026 | More JVM Memory Shells: JVM Memory Shell Auto Searching Program

A Java memory shell is a fileless backdoor that resides entirely in JVM memory, leaving no trace on disk. Attackers exploit code execution vulnerabilities—such as ScriptEngine injection or deserialization flaws—to use Java reflection to replace legitimate objects in web frameworks with malicious classes. Once implanted, specially crafted HTTP requests (mimicking normal traffic) trigger arbitrary command execution within the JVM, with results exfiltrated via standard HTTP responses. This stealthy technique blends seamlessly into legitimate traffic and bypasses firewalls that only allow ports 80/443, rendering traditional reverse shells ineffective. Over the past eight years, common variants have included Tomcat Filter, Tomcat Listener, and Spring Controller memory shells—all dynamically injected at runtime. However, the discovery of new types has largely stalled in recent years, relying almost exclusively on manual source code audits. We have developed an automated framework for discovering Java memory shells, integrating SAST (Static Application Security Testing), Java Agent–based hooking, JVM runtime memory introspection, and AIpowered PoC generation and validation capabilities. This framework dramatically accelerates the discovery of novel memory shells: in a very short time, it expanded the number of known Spring memory shell variants from just 2 to 9. Moreover, it is adaptable to any Java web framework for uncovering new memory shell techniques, significantly enhancing the efficiency of Java memory shell research and surpassing years of manual efforts. Litong Wan | Cyber Security Engineer, Alibaba Holding - Risk & Security Dept Fanghai Yu | Independent Security Researcher, Yang Jing | Cyber Security Engineer, Alibaba Holding - Risk & Security Dept Dongyan Zhang | Senior Security Engineer, Alibaba Holding - Risk & Security Dept Huan Zeng | Senior Security Engineer, Alibaba Holding - Risk & Security Dept https://ift.tt/FJb7ihN

source https://www.youtube.com/watch?v=YIuqIDm1mfk

Black Hat Asia 2026 | Ensuring the Cloud Quantum Computer Runs Your Program… But Learns Nothing

Quantum programs executed on cloud quantum computers expose three critical assets: 1. the input states, which may encode sensitive parameters or proprietary data; 2. the quantum circuit structure, which represents the designer's intellectual property; and 3. the quantum output, the high-value "gold nugget" produced by the computation — such as an RSA private key recovered by Shor's algorithm or the molecular structure of a breakthrough anti-aging drug. Our prior work, ObfusQate, protected quantum circuits by obfuscating their structure so that untrusted compilers cannot infer the algorithmic logic. In this work, we address the third and most valuable threat vector: quantum output theft. We will present a hybrid quantum-classical output-encryption mechanism in which carefully selected quantum gates are inserted before compilation to deliberately corrupt the measurement results that we call quantum encryption. Only the legitimate user — who holds a classical decryption key describing the inserted gates — can reconstruct the true output, classically without the need of a quantum computer. Evaluated across five benchmark algorithms, our approach yields high statistical divergence and strong functional corruption, ensuring that cloud providers cannot learn the output even after running the circuit. The technique is practical, compiler-agnostic, and imposes minimal overhead, making it suitable for protecting quantum IP in untrusted cloud environments. Vivek Balachandran | Associate Professor, Singapore Institute of Technology Amal Raj | Research Engineer, Singapore Institute of Technology https://ift.tt/QDabx7l

source https://www.youtube.com/watch?v=lS4qlzbFN6c

Black Hat Asia 2026 | PhantomRPC: A New Privilege Escalation Flaw in Windows RPC

Windows Inter-process Communication (IPC) is one of the most complex technologies within the Windows operating system. At the core of this ecosystem lies the Remote Procedure Call (RPC) mechanism, which can function as a standalone communication channel or as the underlying transport layer for more advanced inter-process communication technologies. Due to its complexity and broad usage, RPC has historically been a rich source of security issues. Over the years, researchers have identified numerous vulnerabilities in services that rely on RPC, ranging from local privilege escalations to full remote code execution. In this Briefing, I will present a new vulnerability within the RPC architecture that enables a new local privilege escalation technique in all windows versions. This technique allows processes with impersonation privileges to elevate their permissions to SYSTEM level. Although this vulnerability is different from the known "Potato" exploit family, Microsoft has not issued a patch despite proper disclosure. I will introduce five distinct exploitation paths that demonstrate how privileges can be escalated from various local or network service contexts to SYSTEM. Some approaches involve coercion, others require user interaction, and some leverage background services. Because this is an architectural flaw, the number of possible attack vectors is unlimited, any new process or service that depends on RPC may introduce an additional escalation path. For this reason, we will also describe a methodology for identifying such opportunities and constructing custom exploits. This research is intended for vulnerability researchers, exploit developers, red team operators, and defenders seeking to understand, detect, and mitigate these classes of attacks. Haidar Kabibo | Application Security Specialist, Kaspersky https://ift.tt/ZobXLYI

source https://www.youtube.com/watch?v=krztD4lJK30

Black Hat Asia 2026 | Breaking Hybrid Boundaries Across Azure and Windows

Hybrid environments link on premises systems with Azure cloud services, creating a shared management and trust layer that organizations often assume to be secure by design. Our research shows how this assumption can hide critical exposure. During an assessment of Windows Admin Center in both Azure managed and on premises deployments, we uncovered four independent zero day vulnerabilities that can be combined into a full kill chain reaching from the local operating system to the Azure tenant including cross tenant compromise. The issues include a cryptographic flaw that enables unauthenticated cross tenant influence, a local privilege escalation, weaknesses in a modern token verification flow that allow identity and authorization bypass, and a chain of client and server side validation problems that enable remote code execution and complete Active Directory compromise. These findings reveal how a single management service that operates across host, cloud and browser layers can create pathways for movement across boundaries that are normally considered isolated. This presentation will show how attackers can progress from unauthenticated external or internal positions to full administrative control in both environments, and how defenders can identify and break the chain. By viewing the system through the combined lens of trust design, credential handling, and verification logic, the research highlights blind spots in hybrid architectures and shows where similar patterns may emerge in other platforms. Ilan Kalendarov | Security Research Team Lead, Cymulate Ben Zamir | Security Researcher, Cymulate https://ift.tt/NMDFA1C

source https://www.youtube.com/watch?v=41GGT31rA8k

Black Hat Asia 2026 | RebirthDay Attack: Reviving DNS Cache Poisoning with the Birthday Paradox

DNS cache poisoning is a persistent game of attack and defense, posing an enduring challenge for the DNS community. Significant efforts have been made to uncover, detect, and mitigate vulnerabilities that increase the risk of cache poisoning. However, no work has systematically revisited whether the original cache poisoning attack based on the Birthday Paradox remains effective. In this work, we will introduce RebirthDay, a novel DNS cache poisoning attack targeting recursive resolvers and forwarders, reviving the classic DNS Birthday attack that no longer works since 2002. RebirthDay exploits newly uncovered, protocol-compliant vulnerabilities in DNS extension implementations to bypass the query aggregation mechanism intended to prevent DNS Birthday attacks that have not been well understood. We uncovered that 18 out of 22 mainstream DNS software are vulnerable due to weaknesses in the processing of a DNS extension (i.e., ECS option), specifically lacking or incorrectly implemented ECS coherence checks when handling DNS queries and responses, demonstrating the widespread susceptibility to RebirthDay. These flaws could be exploited to circumvent the query aggregation mechanism and launch RebirthDay attacks. Through comprehensive evaluation, we showed that RebirthDay attacks are highly practical and can have significant real-world impact, affecting 16 router vendors, 14 public DNS services, and 365K (15%) open DNS resolvers. We have reported the identified vulnerabilities to affected vendors and discussed mitigation solutions with them. To date, we have received acknowledgments from 8 vendors, including BIND, Unbound, PowerDNS, and Quad9, and have been assigned 50 CVE-ids. Our study emphasizes the need for greater attention to the importance of coherent ECS verification and the DNS extension implementation, revealing new security risks introduced by them. Xiang Li | Associate Professor, Nankai University Yuqi Qiu | PhD Student, Nankai University Mingming Zhang | Assistant Researcher, Zhongguancun Laboratory Zuyao Xu | Master Student, Nankai University Lu Sun | Master Student, Nankai University Fasheng Miao | Master Student, Tsinghua University https://ift.tt/sVxD8k7

source https://www.youtube.com/watch?v=oL12AWOwGRk

Black Hat Asia 2026 | We'll Eat Your Serial for Breakfast

Serial-to-IP converters may sound like "boring" equipment whose only purpose is translating serial data into TCP/IP. Yet they are necessary and ubiquitous: they enable connectivity for medical devices in hospitals, PLCs, sensors and actuators in factories, and RTUs, IEDs and relays in electrical substations. Legacy serial-only devices are not going away any time soon. Attackers do not find them boring at all. In 2015, an attack against Ukrainian power companies intentionally corrupted the firmware of several vulnerable serial-to-IP servers, rendering electrical substations inoperable and causing power outages. Even before that, researchers had reported major vulnerabilities in converters. Now that attacks on global critical infrastructure are more common, we have revisited serial-to-IP converters. To this end, we have: * Quantitatively analyzed firmware from five major vendors, finding outdated components, n-day vulnerabilities and a lack of binary hardening similar to those in less critical devices. * Performed an in-depth analysis of several devices from two major vendors often used in healthcare and OT environments, redacted, where we found 23 new vulnerabilities, some of which allow attackers to take full control of mission-critical devices connected via the serial link. * Used open-source intelligence to find public evidence of these vendors' devices (often with pictures) in electrical substations, water treatment plants and other critical infrastructure. * Connected common serial devices such as temperature sensors, barcode scanners, industrial routers, and patient monitors to these vulnerable converters to demonstrate how easy it is to tamper with their data exchange and what impact that can have. Unfortunately, not much has changed in the last decade. In this talk, we will demonstrate what attackers can achieve when exploiting serial-to-IP converters, which are sometimes less secure than a cheap home router. Stanislav Dashevskyi | Principal Security Researcher, Forescout Technologies Francesco La Spina | Senior Security Researcher, Forescout Technologies https://ift.tt/UofrsL2

source https://www.youtube.com/watch?v=mSiD2TvlyWc

Black Hat Asia 2026 | Bypassing Authentication Reflection Mitigations for SYSTEM Shells

A year ago, authentication reflection vulnerabilities resurfaced as a powerful attack vector through the discovery of CVE-2025-33073. This logical vulnerability allowed taking over almost any Windows machine without any user interaction. Following the official patch by Microsoft, we had a gut feeling that the root cause of the issue was still not addressed. This presentation will cover our journey to bypass the mitigations and pop SYSTEM shells again. In this session, we will start with a reminder regarding the internals of the CVE-2025-33073 vulnerability. We will then build on this to present the generic and iterative bypass methodology that was followed during the research. The methodology will be immediately illustrated by disclosing the first vulnerability that we uncovered: a trivial local privilege escalation via NTLM reflection. Afterwards, we will transition to Kerberos where attack scenarios will be discussed, with both total and partial control of DNS. The attack vector will progressively be refined to finally achieve a full-blown RCE primitive as domain user, via a completely novel Kerberos authentication coercion technique. Throughout this part, in-depth and undocumented details on the inner workings of several specific Windows components will be shared to provide a better understanding of the vulnerability. In the second part, we will dive into how this vulnerability was short-lived and unintentionally patched. Eventually, our methodology will once again be applied to transform it into a privilege escalation vulnerability. The final section will cover the patches' analysis, as well as our thoughts on the current state of authentication reflection vulnerabilities. Guillaume André | Security Researcher, Synacktiv https://ift.tt/OCQGAuU

source https://www.youtube.com/watch?v=EBmssApSYDM

Black Hat Asia 2026 | Cache Me, Catch You: Exploiting LLM Caching Layers in vLLM, GPTCache & Friends

Large language models (LLMs) are now embedded in every cloud, SOC, and product team—but almost nobody is looking at the "boring" cache layer that keeps them fast. In this Briefing, we will show how that invisible layer becomes a powerful offensive entry point. Modern serving stacks such as vLLM, SGLang, GPTCache and commercial gateways aggressively cache prefixes, multimodal features, and semantic embeddings to save GPU time. We performed a systematic teardown of these caching implementations and found that performance shortcuts—non‑cryptographic hashes, lossy serialization, and fuzzy similarity matching—open a brand‑new attack surface during inference, not training. We will walk through six practical attack primitives: system‑prompt hash collisions that silently rewrite assistant instructions for every tenant sharing a cache; block‑wise collisions that make entire malicious blocks "invisible" to the model; multimodal collisions that let a weaponized image inherit a benign cache entry and pass content moderation; and two forms of semantic fuzzy poisoning that turn customer‑support or RAG pipelines into a misinformation delivery channel. Each attack costs under one US dollar to run and, in our experiments, reached up to 100% cache‑hit rate for targeted prompts and 75% poisoned‑hit rate against popular semantic caches. We then flip to the defender's perspective. Based on real patches and CVEs issued by major frameworks, we show what actually works in production: salted and cryptographic prefix hashes, canonical serialization for images and tensors, safer cache isolation in multi‑tenant deployments, and cheap LLM‑based filters that sit in front of semantic caches to kill poisoned hits before users see them. Attendees will leave with a concrete checklist they can apply to their own LLM APIs, gateways, and "AI platform" teams to stop cache‑layer abuses before attackers get there first. We will release PoC tooling that operators can immediately run against their own stacks to detect vulnerable deployments. Xiangfan Wu | Student, Ocean University of China and Tencent Zhuque Lab Lingyun Ying | Researcher, QI-ANXIN Technology Research Institute Guoqiang Chen | Security Researcher, QI-ANXIN Technology Research Institute Yacong Gu | Postdoctoral Researcher, Tsinghua University Haipeng Qu | Professor, Ocean University of China https://ift.tt/MB3CetL

source https://www.youtube.com/watch?v=P0KDHhGLXgE

Black Hat Asia 2026 | How OS, Libraries, and Hardware Keep Your AES Keys Alive

FIPS 140-3 requires cryptographic modules to ensure that sensitive security parameters, including AES keys, are reliably zeroized once they are no longer needed. In practice, however, real systems behave very differently from what this requirement implies. Even when applications appear to implement proper zeroization, surrounding layers such as cryptographic libraries, operating systems, and hardware continue to influence how long keys remain in memory in ways developers cannot easily observe. In this Briefing, we will present the first system-wide, empirical analysis of key zeroization behavior using an FPGA-based live memory forensic technique capable of monitoring physical memory independently of the CPU. By applying this method to Linux and Windows 11 on AArch64 SoC environment (Xilinx KR260) and Intel/AMD PCs with Alinx AXKU3 via Thunderbolt, we uncover several previously unrecognized zeroization failures. AES round keys processed within CPU vector registers are copied into kernel save areas during context switches and remain unzeroized after process termination. Abnormal termination conditions, including signal-based crashes, cause keys to persist for seconds to hours, and distribution-specific crash reporting mechanisms may duplicate them further into core dumps. Most strikingly, we observe that certain systems fail to zeroize memory during reboot, allowing AES keys to survive across system restarts despite expectations derived from FIPS 140-3 guidance. These findings reveal a fundamental gap between the zeroization guarantees assumed during module development and the actual behavior of deployed systems. Our work provides a new methodology for evaluating zeroization on real hardware and offers practical insights for application developers, library maintainers, and OS vendors seeking to meet the intent of FIPS 140-3. Ultimately, we show that zeroization must be validated as a system property, not merely as a software implementation detail. Toyofumi Sawa | Ph.D. Candidate, Institute of Information Security Kuniyasu Suzaki | Professor, Institute of Information Security https://ift.tt/NfcePBa

source https://www.youtube.com/watch?v=r5kkRtEsKT0

Black Hat Asia 2026 | Remote Server, Local Root. Welcome to MCP.

As Large Language Models (LLMs) evolve into autonomous agents, the Model Context Protocol (MCP) has become the de facto standard for connecting AI to external systems. MCP not only enables tool invocation through structured message exchanges, but also supports privileged user-data retrieval from remote servers. To support this, MCP adopts several OAuth-based mechanisms to dynamically establish authorization sessions. However, in doing so, it unintentionally introduces new threat vectors that traditional OAuth applications were never exposed to. In this Briefing, we will uncover a novel attack surface within the MCP authorization flow. By abusing the dynamic nature of this flow, we demonstrate how authorization metadata—traditionally sourced from pre-registered, trusted identity providers—becomes a powerful attack vector when MCP clients accept it dynamically from arbitrary remote servers. Through a systematic analysis of three major classes of MCP clients—browser-based, process-based, and hybrid—we show how this design flaw leads to severe outcomes, including Remote Code Execution (RCE), Local File Execution (LFE), Account Takeover, and Cross-Tenant Data Exfiltration, depending on the client architecture. Our analysis was validated across real MCP implementations and acknowledged by major vendors, including Anthropic and Google. To date, our research has resulted in five assigned CVEs and multiple bounty rewards, including an RCE in MCP Inspector (CVE-2025-58444) and a command injection vulnerability in Google's Gemini CLI. Additional CVEs were assigned to Cherry Studio (CVE-2025-54074), Dify (CVE-2025-58747), and other MCP clients, along with further confirmed impacts across multiple SaaS platforms. Jiacheng Zhong | Security Researcher, Shuyang Wang | Head of Security Research, Obsidian Security Zhengyu Liu | Ph.D. Student, Johns Hopkins University Aonan Guan | Senior Cloud Security Engineer, Wyze Labs https://ift.tt/idtmhnM

source https://www.youtube.com/watch?v=wYcG_6SS788