CVE-2021-33881: On NXP MIFARE Ultralight and NTAG cards, an attacker can interrupt a write operation (aka conduct a "tear off" attack) over RFID to bypass a…
Noroxi assessment
Priority: Monitor (action score 16/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.41% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- 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
On NXP MIFARE Ultralight and NTAG cards, an attacker can interrupt a write operation (aka conduct a "tear off" attack) over RFID to bypass a Monotonic Counter protection mechanism. The impact depends on how the anti tear-off feature is used in specific applications such as public transportation, physical access control, etc.
- Published
- Jun 6, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-863
Report tools
Action score
16
Low priority for now.
- CVSS
- 16 / 40 · 4.2 / 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 | mifare ultralight ev1 firmware | cpe:2.3:o:nxp:mifare_ultralight_ev1_firmware |
| nxp | mifare ultralight ev1 | cpe:2.3:h:nxp:mifare_ultralight_ev1 |
| nxp | mifare ultralight c firmware | cpe:2.3:o:nxp:mifare_ultralight_c_firmware |
| nxp | mifare ultralight c | cpe:2.3:h:nxp:mifare_ultralight_c |
| nxp | mifare ultralight nano firmware | cpe:2.3:o:nxp:mifare_ultralight_nano_firmware |
| nxp | mifare ultralight nano | cpe:2.3:h:nxp:mifare_ultralight_nano |
| nxp | ntag 210 firmware | cpe:2.3:o:nxp:ntag_210_firmware |
| nxp | ntag 210 | cpe:2.3:h:nxp:ntag_210 |
| nxp | ntag 212 firmware | cpe:2.3:o:nxp:ntag_212_firmware |
| nxp | ntag 212 | cpe:2.3:h:nxp:ntag_212 |
| nxp | ntag 213 firmware | cpe:2.3:o:nxp:ntag_213_firmware |
| nxp | ntag 213 | cpe:2.3:h:nxp:ntag_213 |
and 4 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nxp mifare ultralight c firmwareall versions
- nxp mifare ultralight ev1 firmwareall versions
- nxp mifare ultralight nano firmwareall versions
- nxp ntag 210 firmwareall versions
- nxp ntag 212 firmwareall versions
- nxp ntag 213 firmwareall versions
- nxp ntag 215 firmwareall versions
- nxp ntag 216 firmwareall versions
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
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
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.