{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-45492 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-45492 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-45492 is a high-severity vulnerability in n/a, published on 14 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-45492 and fix it if it is affected.\n\nWhat it is: CVE-2021-45492 is a high-severity vulnerability in n/a, published on 14 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-45492 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-45492/ (Markdown: https://insights.sbomify.com/CVE-2021-45492/index.md)","id":"CVE-2021-45492","markdown":"https://insights.sbomify.com/CVE-2021-45492/index.md","name":"CVE-2021-45492","record":{"aliases":["GHSA-gw28-7ffr-r8wm"],"analysis":{"component_type":"desktop_application","fix_type":"configuration_change","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Sage 300 ERP","requires_auth":"low_privilege","summary":"Unprivileged users can escalate privileges to SYSTEM via DLL hijacking due to weak permissions on the installation directory in the system PATH.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sage_300","vendor":"sage"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2021-45492","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2021-45493"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2021-45491"},"products":["n/a"],"published":"2022-07-14","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41397","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41400","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2022-38583","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41398","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41399","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2023-29927","kev_date_added":null,"published":"2023-05-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Unprivileged users can escalate privileges to SYSTEM via DLL hijacking due to weak permissions on the installation directory in the system PATH.","url":"https://insights.sbomify.com/CVE-2021-45492/"}