CVE-2021-45492: High severity sage 300 vulnerability
In Sage 300 ERP (formerly accpac) through 6.8.x, the installer configures the C:\Sage\Sage300\Runtime directory to be the first entry in the system-wide PATH environment variable. However, this directory is writable by unprivileged users because the Sage installer fails to set explicit permissions and therefore inherits weak permissions from the C:\ folder. Because entries in the system-wide PATH variable are included in the search order for DLLs, an attacker could perform DLL search-order hijacking to escalate their privileges to SYSTEM. Furthermore, if the Global Search or Web Screens functionality is enabled, then privilege escalation is possible via the GlobalSearchService and Sage.CNA.WindowsService services, again via DLL search-order hijacking because unprivileged users would have modify permissions on the application directory. Note that while older versions of the software default to installing in %PROGRAMFILES(X86)% (which would allow the Sage folder to inherit strong permissions, making the installation not vulnerable), the official Sage 300 installation guides for those versions recommend installing in C:\Sage, which would make the installation vulnerable.
Affected Software
Event History
Frequently Asked Questions
What is CVE-2021-45492?
CVE-2021-45492 is a vulnerability in Sage 300 ERP (formerly accpac) through version 6.8.x where the installer fails to set explicit permissions for a writable directory.
What is the severity of CVE-2021-45492?
The severity of CVE-2021-45492 is high, with a CVSS score of 7.8.
How does CVE-2021-45492 affect Sage 300 ERP?
CVE-2021-45492 affects Sage 300 ERP (formerly accpac) through version 6.8.x by configuring a writable directory with insufficient permissions.
How can I fix CVE-2021-45492?
To fix CVE-2021-45492, it is recommended to update Sage 300 ERP to a version that addresses the issue.
Where can I find more information about CVE-2021-45492?
You can find more information about CVE-2021-45492 on the Control Gap blog: [https://controlgap.com/blog?tag=insecurity](https://controlgap.com/blog?tag=insecurity) and in the Sage 300 case study: [https://www.controlgap.com/blog/sage-300-case-study](https://www.controlgap.com/blog/sage-300-case-study)