A buffer over-read vulnerability exists in NXP LPC55S69 devices prior to revision A3. When the device is in USB In-System Programming (ISP) mode, a specially crafted GET Descriptor Configuration request with a manipulated wlength value can trigger a buffer over-read, resulting in the disclosure of protected flash memory contents.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides proof-of-concept (PoC) exploit code for CVE-2021-40154, a buffer over-read vulnerability in the USB In-System Programming (ISP) mode of NXP LPC55S69 (RevA2) and Kinetis K82 microcontrollers. The vulnerability allows an attacker with physical access to the device in ISP mode to send specially crafted USB control requests, causing the device to return up to 16KB (LPC55S69) or 64KB (K82) of protected flash memory. The repository contains two main Python scripts, 'LPC_USB.py' and 'K82_USB.py', each targeting one of the affected microcontrollers. These scripts use the 'pyusb' library to communicate with the device over USB, issue the exploitative requests, and save the leaked memory data to local files. The repository also includes binary firmware dumps ('K82.bin', 'LPC.bin') and a detailed README.md explaining the vulnerability, affected devices, exploitation steps, and technical background. The exploit is a local PoC requiring physical access to the device and is not weaponized for remote or automated attacks.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.