CVE-2024-46463 is a vulnerability identified in ORIZON for Windows versions up to 2024.3, involving improper access controls on dedicated folders used by the software. By default, these folders are accessible by other users on the same system, allowing them to misuse technical files contained within. This misconfiguration can lead to privilege escalation, where an attacker with local access but no prior privileges can execute tasks with higher privileges than intended. The root cause is an access control weakness (CWE-276), where folder permissions are not properly restricted, enabling unauthorized users to interact with sensitive files. The CVSS v3.1 score is 7.8, reflecting a high severity due to the potential for significant confidentiality impact and availability disruption. The attack vector is local (AV:L), with high attack complexity (AC:H), no privileges required (PR:N), and no user interaction needed (UI:N). The scope is changed (S:C), indicating that the vulnerability affects resources beyond the initially compromised component. Although no public exploits are known, the vulnerability poses a serious risk if leveraged. Mitigation requires modifying ORIZON's folder permissions to enforce strict access controls, preventing unauthorized users from accessing or manipulating technical files. Organizations should audit their ORIZON installations and apply configuration changes promptly to mitigate this risk.

The vulnerability allows unauthorized local users to access and misuse technical files within ORIZON's dedicated folders, potentially escalating their privileges. This can lead to unauthorized disclosure of sensitive information (confidentiality impact) and disruption or denial of service (availability impact) if critical tasks are manipulated. Since no authentication or prior privileges are required, any local user can exploit this, increasing the risk in multi-user environments or where local access is possible through other means (e.g., compromised accounts or insider threats). The high attack complexity reduces the likelihood of widespread exploitation but does not eliminate risk in targeted attacks. Organizations relying on ORIZON for critical operations may face operational disruptions, data breaches, or unauthorized control over system functions. The scope change indicates that the impact extends beyond the initially vulnerable component, potentially affecting the entire system or network segment.

1. Immediately review and modify the access permissions of ORIZON's dedicated folders to restrict access exclusively to authorized service accounts or administrators. 2. Implement strict file system ACLs (Access Control Lists) that prevent other users from reading, writing, or executing files within these folders. 3. Conduct regular audits of folder permissions and monitor for unauthorized access attempts. 4. Limit local user accounts and enforce the principle of least privilege to reduce the attack surface. 5. If possible, isolate ORIZON installations on dedicated systems or virtual machines to minimize exposure. 6. Monitor system logs for unusual activity related to ORIZON folder access or privilege escalations. 7. Engage with ORIZON vendor support for official patches or guidance and apply updates promptly once available. 8. Educate system administrators about this vulnerability and ensure configuration hardening is part of standard deployment procedures.