CVE-2021-31532: NXP LPC55S6x microcontrollers (0A and 1B), i.MX RT500 (silicon rev B1 and B2), i.MX RT600 (silicon rev A0, B0), LPC55S6x, LPC55S2x, LPC552x…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
NXP LPC55S6x microcontrollers (0A and 1B), i.MX RT500 (silicon rev B1 and B2), i.MX RT600 (silicon rev A0, B0), LPC55S6x, LPC55S2x, LPC552x (silicon rev 0A, 1B), LPC55S1x, LPC551x (silicon rev 0A) and LPC55S0x, LPC550x (silicon rev 0A) include an undocumented ROM patch peripheral that allows unsigned, non-persistent modification of the internal ROM.
- Published
- May 6, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- —
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nxp | lpc55s69jbd100 firmware | cpe:2.3:o:nxp:lpc55s69jbd100_firmware |
| nxp | lpc55s69jbd100 | cpe:2.3:h:nxp:lpc55s69jbd100 |
| nxp | lpc55s66jbd100 firmware | cpe:2.3:o:nxp:lpc55s66jbd100_firmware |
| nxp | lpc55s66jbd100 | cpe:2.3:h:nxp:lpc55s66jbd100 |
| nxp | lpc55s69jev98 firmware | cpe:2.3:o:nxp:lpc55s69jev98_firmware |
| nxp | lpc55s69jev98 | cpe:2.3:h:nxp:lpc55s69jev98 |
| nxp | lpcs66jev98 firmware | cpe:2.3:o:nxp:lpcs66jev98_firmware |
| nxp | lpcs66jev98 | cpe:2.3:h:nxp:lpcs66jev98 |
| nxp | lpc55s69jbd64 firmware | cpe:2.3:o:nxp:lpc55s69jbd64_firmware |
| nxp | lpc55s69jbd64 | cpe:2.3:h:nxp:lpc55s69jbd64 |
| nxp | lpcs66jbd64 firmware | cpe:2.3:o:nxp:lpcs66jbd64_firmware |
| nxp | lpcs66jbd64 | cpe:2.3:h:nxp:lpcs66jbd64 |
and 36 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nxp i.mx rt500 firmwareall versions
- nxp i.mx rt600 firmwareall versions
- nxp lpc5512jbd100 firmwareall versions
- nxp lpc5512jbd64 firmwareall versions
- nxp lpc5514jbd100 firmwareall versions
- nxp lpc5514jbd64 firmwareall versions
- nxp lpc5516jbd100 firmwareall versions
- nxp lpc5516jbd64 firmwareall versions
+12 more rows
- nxp lpc5516jev98 firmwareall versions
- nxp lpc5526 firmwareall versions
- nxp lpc5528 firmwareall versions
- nxp lpc55s14jbd100 firmwareall versions
- nxp lpc55s14jbd64 firmwareall versions
- nxp lpc55s16jbd100 firmwareall versions
- nxp lpc55s16jbd64 firmwareall versions
- nxp lpc55s16jev98 firmwareall versions
- nxp lpc55s26 firmwareall versions
- nxp lpc55s28 firmwareall versions
- nxp lpc55s66jbd100 firmwareall versions
- nxp lpc55s69jbd100 firmwareall versions
Same product
nxp: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-40154NXP LPC55S69 devices before A3 have a buffer over-read via a crafted wlength value in a GET Descriptor Configuration request during use of…22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.