Root code execution by privileged local users
Published Nov 5, 2024 · Updated Jan 9, 2026
Privilege escalation in 2N Access Commander 3.1.1.2 and earlier allows local users to execute arbitrary code with root permissions. The published record maps the flaw to improper validation of an integrity-check value but does not identify the affected component or incorrect validation operation. Exploitation requires existing high privileges, local access, no user interaction, and high-complexity conditions; root execution can expose data and alter system state.
Summary
What happened
Privilege escalation in 2N Access Commander 3.1.1.2 and earlier allows local users to execute arbitrary code with root permissions. The published record maps the flaw to improper validation of an integrity-check value but does not identify the affected component or incorrect validation operation. Exploitation requires existing high privileges, local access, no user interaction, and high-complexity conditions; root execution can expose data and alter system state.
The record
- CVE
- CVE-2024-47255
- Published
- Nov 5, 2024
- Updated
- Jan 9, 2026
- Vendor
- 2N
- Product
- 2N Access Commander
- Classifications
- CWE-354, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 2024CVE 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=0 <=3.1.1.2
- Affected versionversion=<=3.1.1.2
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.
Weakness, pattern, technique
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