CVE-2024-37386: Improper Access Control
Source CVE Database V5
Not known to be exploited · CVSS 4.2 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Jul 2024
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
AI-suggested
To mitigate CVE-2024-37386, organizations should immediately upgrade affected Stormshield Network Security devices to the fixed versions 4.3.27, 4.7.6, or 4.8.2 as appropriate. In addition to patching, network segmentation should be enforced to restrict access to SNS management interfaces and reduce the attack surface. Implement strict access control lists (ACLs) to limit which hosts can communicate with SNS devices, especially on management ports. Monitor device logs and network traffic for unusual restart patterns or attempts to enter single-user mode. Employ multi-factor authentication and strong password policies for device administration to reduce risk if unauthorized access is attempted. Regularly audit device configurations and firmware versions to ensure compliance with security policies. Finally, maintain an incident response plan that includes procedures for SNS device compromise scenarios to enable rapid containment and recovery.
Description
An issue was discovered in Stormshield Network Security (SNS) 4.0.0 through 4.3.25, 4.4.0 through 4.7.5, and 4.8.0. Certain manipulations allow restarting in single-user mode despite the activation of secure boot. The following versions fix this: 4.3.27, 4.7.6, and 4.8.2.