CVE-2024-13417: 2N OS · Uncaught Exception
Affects 2N OSSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| 2N 2N OS | Affected
| Fixed in– |
AI-suggested
- Immediately update all 2N RFID-equipped devices to 2N OS version 2.46 or later, which contains the fix for this vulnerability.
- Restrict network access to the RFID reader interfaces to trusted and authenticated management networks only, minimizing exposure to untrusted actors.
- Implement network segmentation and firewall rules to isolate access control devices from general user networks and the internet.
- Monitor device logs and network traffic for unusual or malformed payloads targeting RFID readers that could indicate attempted exploitation.
- Establish operational procedures for rapid device restart or failover in case of detected denial-of-service conditions.
- Coordinate with 2N support for firmware updates and security advisories to stay informed of any emerging threats or patches.
- Conduct regular security audits and penetration testing focused on physical access control systems to identify and remediate potential weaknesses.
Description
Specifically crafted payloads sent to the RFID reader could cause DoS of RFID reader. After the device is restarted, it gets back to fully working state.2N has released an updated version 2.46 of 2N OS, where this vulnerability is mitigated. It is recommended that all customers update their devices to the latest 2N OS.