Skip to main content
VulnerabilityPublished Updated

CVE-2024-47255: 2N Access Commander · Improper Validation of Integrity Check Value

Affects 2N Access CommanderSource CVE Database V5

0

Not known to be exploited · CVSS 4.7 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
2N 2N Access CommanderAffected
  • <=3.1.1.2
Fixed in–

AI-suggested

  1. Restrict local access to systems running 2N Access Commander to trusted administrators only, employing strict access control policies and monitoring.
  2. Implement robust logging and alerting for privilege escalation attempts and unusual system behavior on affected hosts.
  3. Use host-based intrusion detection systems (HIDS) to detect unauthorized changes or execution of suspicious code.
  4. Regularly audit user privileges and remove unnecessary high-level access to minimize the attack surface.
  5. Apply vendor patches or updates as soon as they become available; monitor 2N communications for patch releases.
  6. Consider network segmentation to isolate physical access control systems from general IT infrastructure, reducing lateral movement risk.
  7. Employ multi-factor authentication for administrative access to reduce the risk of credential compromise.
  8. Conduct security awareness training for administrators to recognize and report suspicious activities.
  9. If patching is delayed, consider temporary compensating controls such as disabling unnecessary services or restricting execution permissions on critical files related to integrity checks.

Description

In 2N Access Commander versions 3.1.1.2 and prior, a local attacker can escalate their privileges in the system which could allow for arbitrary code execution with root permissions.

References

Community reviews

Loading reviews…