RFID reader crash via crafted payload
Published Feb 6, 2025 · Updated Jan 9, 2026
Uncaught exception in the RFID reader in 2N OS 2.45 and earlier allows physically proximate attackers to crash the reader. The reader leaves an exception uncaught while processing a specially crafted RFID payload; 2N has not disclosed the affected parser or payload field. Physical access to the RFID interface is required, and exploitation stops reader operation until the device is restarted.
Summary
What happened
Uncaught exception in the RFID reader in 2N OS 2.45 and earlier allows physically proximate attackers to crash the reader. The reader leaves an exception uncaught while processing a specially crafted RFID payload; 2N has not disclosed the affected parser or payload field. Physical access to the RFID interface is required, and exploitation stops reader operation until the device is restarted.
The record
- CVE
- CVE-2024-13417
- Published
- Feb 6, 2025
- Updated
- Jan 9, 2026
- Vendor
- 2N
- Product
- 2N OS
- Classifications
- CWE-248, T1499
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2025CVE publishedPublication date reported by the CVE source.
- Jan 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2N RFID equipped products running 2N OS 2.45 and prior
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo