With 23.5.0 patching the ns2jb filesystem escape, I’ve been thinking about offline entry points that don't rely on specific eShop games getting delisted. Has anyone looked into using a programmable microcontroller (like an ESP32) acting as a third-party controller to target the Change Button Mapping or Update Controllers menus in System Settings? The basic idea: When you open the button mapping menu, the Switch 2 reads the controller’s hardware descriptors, layout info, and device strings, then writes custom presets to system save data. A spoofed USB or Bluetooth controller could feed malformed HID descriptors, out-of-bounds button counts, or oversized strings during that handshake to see if the Settings UI parser crashes or overflows. Similarly, reporting a fake outdated firmware version could let the controller send unexpected packets during the "Update Controllers" check. Even though the Settings applet is sandboxed in userland and would still need a kernel exploit to pair with, a controller-based trigger would work completely offline on any stock 23.5.0 console without needing a specific game. Has anyone fuzzed the remapping UI yet?   submitted by   /u/The_DiGital-Hero [link]   [comments]