CVE-2024-13416: 2N OS · Sensitive Data in Logs
Affects 2N OSSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation 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
The primary mitigation is to upgrade all affected 2N OS devices to version 2.46 or later, where the vulnerability has been fixed. Additionally, organizations should audit and restrict access to system logs to minimize the risk of token exposure. Implement strict role-based access controls (RBAC) to limit who can enable logging features and access logs. Regularly review and sanitize logs to remove sensitive information where possible. Employ network segmentation to isolate 2N OS devices and their logs from broader network access. Monitor for unusual logging activity or unauthorized changes to logging configurations. Finally, enforce strong authentication and credential management policies to reduce the risk of authorized user accounts being compromised.
Description
Using API in the 2N OS device, authorized user can enable logging, which discloses valid authentication tokens in system log.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.